Tidal Enterprise Scheduler (TES) TESCache DB and High Availability (HA) performance

[fgannon01]

We are currently running TES Version 6.1.0.533, and experiencing a performance issue with this product. We have the DB's (Admiral & TESCache) both configured to run in High Availability (HA). With this configuration, once we have more than 6 or 7 associates log into Tidal, the application becomes extremely slow.

Question: Is anyone using TES w/High Availability, and if so... how did you get it to work?  any special configuration settings, etc?

FYI... Resources: e.g.: Mem/RAM/Storage/CPU are all within specs for Med - Large config.

Thanks,

Fred Gannon

FGannon@west.com

[Joe Fletcher]

I'd suggest going to 6.2.1 patched up to the eyeballs There have been some big improvements in performance and the new java client is actually pretty nice.

A big win was swapping ojdbc7.jar to ojdbc6.jar which I think is something you can do in 6.1.

For us it turned the web client from borderline useless to very effective.

[Asim Faruki]

Hi Joe. Wondering how much memory the Java client requires to work effectively. I'm concerned this will require a huge memory footprint for each client.

Regards

Asim

asim.faruki@hays.com

[Joe Fletcher]

Spec says 8Gb or more and tbh it needs it. You can think of it like a self-contained client manager and browser rolled into one.

So yes, you will need to spec up the desktops running it.