Sven Steiniger wrote:
Hi!
I used Slide in project for half an year now and as it
get's finished now, I tried to tweak it for more performance
(settings: content store to local file system, others into database).
When inserting files in Slide, there are four hotspots consuming
about 80% of the used time:
1 NodeLock
2 ObjectNode
3 NodeRevisionNumber
4 JDBCDescriptorsStore
Optimizing those spots resulted in a speedup of factor three!
1-3 are really simple and have no side effects at all. Shall
I simply check-in the changes or is there someone who first
controls them?
The optimization on JDBCDescriptorsStore is also simple and
relates to the isConnect()-method. I have read a lot of discussions
on this topic but maybe it's worth to start this thread again.
This method causes a major slowdown because of executing a
statement for every simple operation.
I understand that it is necessary to ensure the 100% data integrity,
but in normal environment it's very unlikely that the database
connection is lost. Thus in general it should be safe enough to check
the connection about every minute.
So why not introducing an option in the domain-config where the
connection-checking can be configured? Thus every project can choose
the appropriate settings.
All this look like good ideas IMO.
Remy
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
