Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
HomeAnnouncementsFree MagazinesWhite PapersSubmit Content
Discussion GroupsASP.NETWindows FormsLanguages.NET FrameworkVisual Studio.NET
Articles.NET FrameworkASP.NETToolsWindows Forms
.NET DirectoryOpen Source ProjectsUser GroupsWeb Resources
Related Topics
Visual Basic 6SQL ServerMS AccessOther DB ProductsMS Server ProductsMore Topics ...

.NET Forum / .NET Framework / Performance / January 2005

Tip: Looking for answers? Try searching our database.

JIT Compiler identified as  major Processor overhead, Solutions?

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
Neal - 18 Jan 2005 13:33 GMT
Hi

Using v1.0, and a straightforward app, ie WebForms, Grids and MSSQL calls
into Datasets / SQLDataReaders.
On Testing (granted test server is a P2 350mhz), The Processor Counter shows
MAxing out at 10 concurrent users, all other counters are at absolute idle.
(DB on a seperate DB Server), recordsets are no that vast.
I used AQTime to interrogate the Rtns for time taken with children processes
and %time taken.
At the most granular level, JIT compilation was taking 3.34 ms average time
to 0.02 of any of the other rtn's. (eg SqlDataAdapter::.ctor, an
DBDataAdapter::.ctor and SqlParameterCollectio::Add)
The JIT Compiler rtn with children processes was as high as 29.38 ms vs 0.19
to .05 for the others ((eg SqlDataAdapter::.ctor, an DBDataAdapter::.ctor and
SqlParameterCollectio::Add)

Is there anything I can do, to improve this? (decent server firstly true), I
get totally different readings when doing performance counter checks against  
my dev laptop, (1.8, 256 ram).,
Has it to do with CPU caching and processing speeds on the P2 dev Web
machine ??
Thanks
Neal

JIT Compilation and  

Signature

Neal Rogers
University of Cape Town

David Browne - 18 Jan 2005 13:50 GMT
> Hi
>
[quoted text clipped - 17 lines]
> and
> SqlParameterCollectio::Add)

This is not your problem.  JIT happens only at startup.  Let your app run
for a while before you start profiling.

Also look at the ".NET CLR Memory/% Time in GC" counter.  ASP.NET and
DataSets in particular generate a lot of garbage. If you have too little ram
on your server, you might be spending a lot of time in garbage collection.

David

Free Magazines

Get these publications absolutely FREE for up to 12 months. There are no hidden fees and no obligation. Simply choose a title, complete the application form and submit it. Read more ...

Oracle MagazineNetwork ComputingComputer WorldBio-IT WorldeWeekInformation WeekInfosecurity
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2008 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.