Hi Robert, Under our current load of course we do not see this, as the writes per second are minimal, we are much more concerned with reads. Also the Controllers we are using are not as powerful as the backends databases.
> The backlog should disappear if you switch the log to write to a more > capable database such as MySQL. MySQL by contrast can perform 2000 > or more updates per second on a single thread without difficulty. > You correctly noted, by the way, that there is a single connection. > We use either MySQL or PostgreSQL in the commercial products based on > Sequoia. > > The recovery log is written asynchronously, so it does not at least in > theory have too much impact on SQL update rates. However, Hypersonic > is pretty slow and uses a lot of memory when you have large > quantities of data. Switching to an external database should speed > things up at least a bit. What amount of memory do you suggest allocating to Sequoia on startup, currently we are setting 768 and max of 1024, and if we were to increase this, is their a noticeable performance increase? When your refer to external database, do you mean external to the server that sequoia sits on. Regards, Stuart _______________________________________________ Sequoia mailing list Sequoia@lists.forge.continuent.org https://forge.continuent.org/mailman/listinfo/sequoia
