Loading

Subscribe to this Blog

Your email:

Are you preparing for an implementation or upgrade?

Kronos Implementation Strategy

Download the WFM Implementation Strategy White Paper

About Bryan

Resume Pic of Bryan deSilvaMusician & Yin Style Bagua practitioner. Over twenty years of software implementations and upgrades, project management, systems and applications development experience with a current focus on ADP eTime & Kronos Timekeeper/HR systems implementation. 

The "Kronos Guy" Blog

Current Articles | RSS Feed RSS Feed

Kronos can have multiple Callable Totalizers

  
  
  
  
  
  
  
Would you like Dramatic Response Time Improvements?

WFC v5.1 and below:

Most Kronites know that this is the routine Workforce Central Timekeeper uses to calculate totals interactively when viewing employees. It invokes the Totalizer just for those employees whose totals have not yet been computed by the Background Processor (not up to date.) It doesn’t do anything with these results except display them on the screen. They are tossed out when done. They don’t update the database. They are just for the users viewing pleasure. Did you know that it’s used also by Group Edits to calculate totals and by Accruals to calculate accrual balances? It’s an important little process.

There are several settings available but the most important one to understand is site.totalizer.number_of_engines. Yep, you read that correctly. One can have multiple Callable Totalizers. Imagine the power! I’ve had success with up to four. To quote the brilliant Kronos docs:

"After the system is running, multiple Callable Totalizers can provide fast totalization requests throughput than a single Callable Totalizer can. Four Callable Totalizers may produce totalization request throughput that is four times as fast!" (emphasis mine)

Give it a try. If you have over 1000 emps I expect your users will notice a significant response time improvement with as few as two, more than 3-4000 emps and I suggest four. Of course your mileage may vary. It depends mostly on how many users are actually working on the system at the same time, not the employee population.”

Watch for some thoughts on the totalizers from 5.2 and newer in a later post! 

Reprinted from Improv's TNT written 12/11/08

Comments

Would you be able to tell me where I can find that Kronos article? 
 
I'd like to read more. Also, what versions of Kronos does it apply to? 
 
Thanks for your assistance.
Posted @ Tuesday, June 08, 2010 12:00 PM by Alex Lopez
I should have been more clear. Heck, there really isn't even a CT in 5.2+ The so-called Callable Totalizer was an artifact of the Smalltalk implementation of the totalizer in 5.1 and earlier. From 5.2 onwards, all on-the-fly totalization goes through the same (multithreaded) totalizer servlet stuff. 
 
The CT still exists but... This article was posted for versions prev to 5.2 when the rewrite of the totalizer was completed. There is a follow up article being posted atwww.improvizations.com/kronosblog/ in the next few weeks talking about 5.2 and later.
Posted @ Tuesday, June 15, 2010 9:05 PM by Bryan deSilva
Post Comment
Name
 *
Email
 *
Website (optional)
Comment
 *

Allowed tags: <a> link, <b> bold, <i> italics