From: Walden H. Leverich
Yup. But if you have 1000 users you'll have the machine to handle
1000 users.

Well, maybe you have 1,000 users and 40 pre-fork jobs. When one job is busy a request is dispatched to the next. Over time, user requests will be dispatched to all the pre-fork jobs. 1,000 users could lead to 40,000 permanant connections - unless constrained by a DB setting.

My concern is on 100,000 users, but then you're not likely to
give each their own i user/password, rather run as a "WebUser"
userprofile.

That's what I suspect most developers will do. But then you lose the visibility in journals of which users are performing which database updates. And I sometimes store Last-Update-User, and show it on screens. A feature like that would take a hit.

Nathan.





As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.