Databases
StackOverflow2013
Postsdbo
POThreads processing a batch job in servlet enviornment
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POThreads processing a batch job in servlet enviornment
    primarykey
    data
    text
    <p>I have a Spring-MVC, Hibernate, (Postgres 9 db) Web app. An admin user can send in a request to process nearly 200,000 records (each record collected from various tables via joins). Such operation is requested on a weekly or monthly basis (OR whenever the data reaches to a limit of around 200,000/100,000 records). On the database end, i am correctly implementing batching.</p> <ul> <li><p>PROBLEM: Such a long running request holds up the server thread and that causes the the normal users to suffer.</p></li> <li><p>REQUIREMENT: The high response time of this request is not an issue. Whats required is not make other users suffer because of this time consuming process.</p></li> <li><p>MY SOLUTION:</p> <p>Implementing threadpool using Spring taskExecutor abstraction. So i can initialize my threadpool with say 5 or 6 threads and break the 200,000 records into smaller chunks say of size 1000 each. I can queue in these chunks. To further allow the normal users to have a faster db access, maybe I can make every runnable thread sleep for 2 or 3 secs. Advantages of this approach i see is: Instead of executing a huge db interacting request in one go, we have a asynchronous design spanning over a larger time. Thus behaving like multiple normal user requests.</p></li> </ul> <p>Can some experienced people please give their opinion on this? I have also read about implementing the same beahviour with a Message Oriented Middleware like JMS/AMQP OR Quartz Scheduling. But frankly speaking, i think internally they are also gonna do the same thing i.e making a thread pool and queueing in the jobs. So why not go with the Spring taskexecutors instead of adding a completely new infrastructure in my web app just for this feature?</p> <p>Please share your views on this and let me know if there is other better ways to do this? Once again: the time to completely process all the records in not a concern, whats required is that normal users accessing the web app during that time should not suffer in any way. </p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USSahil Muthoo
    1. UShellojava
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POThreads processing a batch job in servlet enviornment
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POThreads processing a batch job in servlet enviornment
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. POThreads processing a batch job in servlet enviornment
      1. USCarlos Jaime C. De Leon
      1. VTFavorite
    1. COHow are the jobs structured? Is it one big stored procedure or are you going through an ORM? Please elaborate this "on the database end, I am correctly implementing batch"?
      singulars
      1. POThreads processing a batch job in servlet enviornment
      1. USSahil Muthoo
    2. COIts handled via the ORM and not with a stored procedure.
      singulars
      1. POThreads processing a batch job in servlet enviornment
      1. UShellojava
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload