akloaklo
Supremacy Member
- Joined
- Nov 15, 2004
- Messages
- 7,252
- Reaction score
- 19
I'm currently writing a task manager for my company.
The task manager will write to a table if a particular task was ran successfully.
It is highly possible that there will be at least 200 task per day and sometimes even 800 task in the span of 2-3 hours (or even 1hour)
Like I mentioned, for each task, I will have to update/insert/read data to my task table to change the status and some other variables.
So my code is currently:
conn.open()
//do things for each task (could even be concurrent task)
conn.close()
I'm using just Java (not J2EE) and my app NOT be running from an app server, it will just be a jar file which will be executed on a machine.
So how do you determine if I need pooling or not? How many connections are considered many?
Edit: it also seem that for db connection pooling, people only implement it on appserver like apache/tomcat? Is there no need to implement pooling for a program that simply just run without an appserver?
The task manager will write to a table if a particular task was ran successfully.
It is highly possible that there will be at least 200 task per day and sometimes even 800 task in the span of 2-3 hours (or even 1hour)
Like I mentioned, for each task, I will have to update/insert/read data to my task table to change the status and some other variables.
So my code is currently:
conn.open()
//do things for each task (could even be concurrent task)
conn.close()
I'm using just Java (not J2EE) and my app NOT be running from an app server, it will just be a jar file which will be executed on a machine.
So how do you determine if I need pooling or not? How many connections are considered many?
Edit: it also seem that for db connection pooling, people only implement it on appserver like apache/tomcat? Is there no need to implement pooling for a program that simply just run without an appserver?