OK,
I now believe that I am staring at a simple fact. The PERFORMANCE IN
CONTAINERS IS BOLONEY!
Our container can run in 0.05ms (yes **m**s) and still excercise 80 of its
features. what costs a lot is **serialization** and we find that in JDBC
calls and network calls.
It appears that our JDBC calls are not optimized at all. We know it is just
JawsCMP but it is what people really look at when they work on JBoss. There
are tons of optimizations such as using "raw" ids in the database (Oracle).
The way we would work this is that we could then map the primary keys to the
raw ID (simple map) and the lookups would be kick ass fast.
I believe we also implement correctly the "isModified", but we could really
do a "getModified" that would return the names of the modified fields. We
could then bypass the "tuned" updates.
Finally the load today is very blind and very stupid. We just load
everyone. A simple implementation of the "versioning" pattern in the
database (where we add a field that is the version of the record) enables us
to get the right version in little time and saves us time in loading since
we can just "select version where rawID" for example :)
If you are interested in leading this effort and have serious db background
please let the board know
marc
_________________
Marc Fleury, Ph.D
[EMAIL PROTECTED]
_________________
_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-development
