And GOD knows those licenses cost a freaking fortune. p.
> 200 simultaneous users, and 200 user sessions are 2 different things > to me. The second is just a matter of having enough memory in your > server. The first is managed by adding more servers to your load group. > > As far as odbc spawning, I have seen this related MOSTLY, like 90% to > the odbc driver and they way it works for a particular db. Witango > requires a certain amount of memory for each connection, that is one > consideration. The other is your db. It is usually on the db side > where problems occur. I have seen a single witango server open 50+ > server connections to a single db under load, it may hang stuff up, > but probably cuz your server is running out of memory, and its > effecting its ability to perform and respond to queries, thus hanging > your witango server. Or it exceeds your connection maximum, forcing > witango to hang, cuz it can't open a connection, or error. > > When you start growing, and taking on a load, you have to consider > how this effects the entire picture. I can tell you that witango 5.5 > scales with ease. Give it enough memory, and add more to your load > group as your traffic increases. Also, can your db handle the load > witango is throwing at it. > > One last thing, many people have asked me in the past, why I spend so > much time comparing methods, benchtesting with timers and so forth. > It is because I have gone through a lot of my own experience, and > have been hired to help others with there witango installations. > > 90% of the time issues are traced to code errors and inefficiencies. > I can't tell you how many times I have seen witango servers hang, and > users complain about witango crashing, and I found an "include empty" > parameter set to false in a search action, that under certain > conditions causes an entire table scan on the db of a large table and > just brings the whole system to its knees. If you don't know what I > am referring to, read and understand what the little parameter does. > I have seen that one thing bite more people in the a$$ than anything > else. Including me. > > There is no magic number as to how many concurrent sessions a witango > server can handle, most people would say, 50. But there are so many > factors. Server hardware, network card and switch, db speed, and the > list goes on. But I would put CODE as the top factor. If you are just > doing small queries and returning rows, with decent hardware, you can > probably handle 100, but if you are calculating the energy effeciency > of your home, with 100 input variable (nod to LBL) you may be able to > handle 10. It all depends. But code efficiency should take most of > our focus. It makes our apps run better, snappier, and saves us money > on bigger dbs and witango licenses. > > -- > > Robert Garcia > President - BigHead Technology > VP Application Development - eventpix.com > 13653 West Park Dr > Magalia, Ca 95954 > ph: 530.645.4040 x222 fax: 530.645.4040 > [EMAIL PROTECTED] - [EMAIL PROTECTED] > http://bighead.net/ - http://eventpix.com/ > > On Apr 28, 2006, at 6:40 AM, Fogelson, Steve wrote: > >> I had a sight last night that SearchPublisher 3.0 was indexing. I >> am sure they are similar to other search engines in that each >> request invokes a new user session. Imagine if you have 15 to 20 >> sites on a Witango server, the normal 30 minute session inactivity >> variable purge, normal traffic for each site and a few search >> engines start indexing the sites. User sessions can exceed the 200 >> sessions that Andre talked about real quick. > > > ________________________________________________________________________ > TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf ________________________________________________________________________ TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf
