Thanks for the feedback. I understand you're probably killing these servers doing this intense processing... but what about # users? Is it one guy running intense simulations... I'm curious about # requests per minute type of loads.
Thanks, Aaron
Jason McKerr wrote:
I've also worked with OJB on high-load situations in J2EE environments. We're using JRun and/or Orion with OJB in a clustered/distributed
environment. This is a National Science Foundation project called the
Network for Earthquake Engineering Simulation (NEES).
The only major problem that we ran into was the cache. JCS just isn't good, and hasn't seemed to get much better over the last year. We ended up plugging in Tangosol's Coherence Clustered Cache into the system. We can also do write-behinds, and buffered data caching that is queued for transaction. That's important to us because we're dealing with very expensive scientific data that _can't_ get lost if a db goes down. Some of these Tsunami experiments can get pretty expensive.
Otherwise, we use mostly the PersistenceBroker, and a little of the ODMG. Performance seems better on PB, but less functional. It's not really that much of a problem anyway, because we can cheaply and quickly add app-servers to the cluster.
Jason
On Thu, 2003-06-12 at 22:14, Aaron Longwell wrote:
I realize I may be comparing Apples to Enterprise Applications here, but I'd like to hear some feedback about using OJB in high-load (load balanced?) environments.
On an OJB web application, how many requests have you seen an application handle? Would anyone be concerned about using OJB on an enormous e-commerce site? (EBay, Amazon, etc)?
Thanks for the input, Aaron
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
