Re: Query result times in WO and mysql
Re: Query result times in WO and mysql
- Subject: Re: Query result times in WO and mysql
- From: Klaus Berkling <email@hidden>
- Date: Wed, 21 Jan 2004 08:22:28 -0800
On Tuesday, January 20, 2004, at 06:06 PM, Lon Baker wrote:
One last comment on using raw rows to much, and I am sure someone here
will correct me if I am wrong, raw rows are never cached. This means
as you try to scale your application you will see the bottleneck
develop quickly on the MySQL side. My initial overuse of raw rows saw
MySQL peg out the CPU and cause big delays as I added more users. In
my case a single page that needed to refresh every 90 seconds made a
number of queries for lists of raw rows.
The client, which is not a web browser, is suppose to do its own
caching. Another person's project :-) . A different
client/connection/session would mean an entirely new and different
query.
In the long run I like to eliminate the client and replace it with a
web browser but thats far off. That should reduce the number of
transferred records and increased perceived speed.
Anyway sorry I was so long winded just wanted to share what I have
found.
My 2".
Thanks for your thoughts.
kib
_______________________________________________
webobjects-dev mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/webobjects-dev
Do not post admin requests to the list. They will be ignored.