Well, Ian, a last rundown :-) -----Original Message----- From: Ian Griffiths [mailto:[EMAIL PROTECTED]] Sent: Dienstag, 7. Mai 2002 12:09 To: [EMAIL PROTECTED] Subject: Re: [DOTNET] ASP.NET's Application object: does it scale?
<...> What's your measure of 'traffic' by the way? You seem to be suggesting that *** Gigabytes? for a given number of page impressions, a mostly static site has more 'traffic' than a mostly dynamic site. A dynamic site will be busier, sure, because it has to work harder, but that's not a measure of 'traffic' in any sense that I understand. *** No. I was basically pointing out that MS probably has more traffic than most other sites due to the massive amount of DOWNLOADS going on there. I was pointing out that this might be the reason for their extreme bandwidth with JUST this small number of page impressions. Anyway, to try and drag this back onto the topic of the original question, I think the question was whether the application object represented a scalability issue. If you're getting 35 page views a second, then regardless of whether you think that's piffling or massive, it's definitely going to be enough to mean that locking on the application object could be a bad idea. In particularly you absolutely would not want to lock it for the *** FULL ack here. Though this CAN start to be a problem with WAY less pages per second. I recall an application I once was monitoring a rework on where the stupid idiot of developer (really, I mean THIS) had ONE database connection for the whole app that was stored in the application object, and every access and use was wrapped with a lock. And they wondered this intranet app did not scale :-) whole time it takes to serve a page up. (Well duh... But that would be a no-brainer solution to thread safety for accessing the Application object. I've seen worse...) *** Absolutly. BUT - app objects not necessarily need to be locked on the application object level :-) Regards Thomas You can read messages from the DOTNET archive, unsubscribe from DOTNET, or subscribe to other DevelopMentor lists at http://discuss.develop.com.
