Atomikos Forum

StreamObjectLog.flush, delete big hot spots - avoid?

I am new to Atomikos and JTA in general and have the following stack:

Hibernate 3.3.1.GA (Spring-managed)
Spring 2.5.6
JBossCache 3.0.2
Tomcat 6
Atomikos Essentials (Spring-managed)

I had to add JTA to accommodate JBossCache (write case). (Purely for notification of Synchronizations - nothing more) I ran a load test with 50 users making concurrent requests for some data and after Atomikos was added read performance worsened by a factor of 15x.

The hot spots are StreamObjectLog.flush and delete methods (that are synchronized).

How should I configure Atomikos to see best-case performance? I take it I need to disable tx logging; anything else?

thanks
-nikita
Nikita Tovstoles Send private email
Friday, February 13, 2009
 
 
Did you try with our 3.5 release? It has some extra optimizations wrt logging.

HTH
Guy Pardon Send private email
Wednesday, February 18, 2009
 
 
Guy,

Turns out we *were* having two simultaneous conversations: on this forum as well as here:
http://forum.springframework.org/showthread.php?t=67597

Since I don't have your e-mail address I am e-mailing the JProfiler snapshot to Atomikos support. Please lmk if I should be sending it elsewhere.

-nikita
Nikita Tovstoles Send private email
Thursday, February 19, 2009
 
 

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics