• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Jeanne Boyarsky
  • Ron McLeod
  • Paul Clapham
  • Liutauras Vilda
Sheriffs:
  • paul wheaton
  • Rob Spoor
  • Devaka Cooray
Saloon Keepers:
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
  • Frits Walraven
  • Tim Moores
Bartenders:
  • Mikalai Zaikin

Data intensive processing

 
Greenhorn
Posts: 1
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hi,

We are developing a payroll application and intend to use hibernate as an option to make our application DB independent. The payroll calculation is quite data intensive and can have about 300,000 - 500,000 records being processed at a time. Runs in multiple level loops (atleast 3) and needs to refer multiple rate tables depending on the task performed and being calculated. it also has multiple sets of calculation that needs to be done with different references. Effectively a fully fledged payroll activity based application. Few calculations that can be considered are task based, overtime, statutory (tax and PF), leave pay, holiday pay, other allowances. All for 3 different types of worker types, may or may not have similar pay structure.

Our target to process this is 5 minutes.

My queries are,

1. Is Hibernate a suggested environment for this task?
2. How effective is HQL when compared to the database programming with SQL?
3. What are the considerations that we need to have to ensure we achieve optimum performance?

Do let me know if you need any further information for this.

Thank You
Shabeer
 
Ranch Hand
Posts: 624
9
BSD Java
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
If my requirement is such that, I have to execute a second query depending on the result of first query, then execute third query depending on the result of second query...
then I prefer stored procedure.
It considerably reduces the processing time.
 
Greenhorn
Posts: 7
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
I would have used Stored Procedure with Transaction. In such situation Stored Procedure would be optimum.
reply
    Bookmark Topic Watch Topic
  • New Topic