On 8. Apr. 2009, at 17:04 , Chuck Hill wrote:
At the moment each page access writes to the database as a page
access log - so the connection is heavy used for updates/inserts.
So ..... what do you thing the best practice would be to improve
performance?
First, I'd avoid an insert/update per RR loop just for an access
log. Write it out to disk instead. Or at least queue up a message
for another thread to use JDBC to write this out.
In the past I've done the same, writing to PostgreSQL and FrontBase
databases for logging those things, and I have to say, it is
convenient, but performance, especially with FrontBase got an issue
when we hit a couple of million rows. The inserts got slower and
slower and brought performance down. FrontBase is not really fast
inserting into tables when there are a couple indexes on that table -
which we had. Dropping those indexes helped, but overall, performance
was bad. PostgreSQL didn't show this behaviour, inserts were always
fast.
Nevertheless I agree to go the logging to a file route - either with a
specific log4j appender for those messages, or, if it has to be in the
database, maybe with a log4j jdbc appender (haven't tried that one
though).
The performance appears to have gotten worse with WO5.4. Is that
possible?
I have not noticed that, but is possible that you are doing
something that is affected by changes in 5.4. I can't think of
anything specific.
It might be, depending on the database plugin that is used and the
database itself, that the SQL is different now and needs different
indexes.
cug
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list ([email protected])
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com
This email sent to [email protected]
