If I understand your code correctly, for each row update, you would have to wait for five seconds at worst or hundreds of milliseconds at best (time needed to get a page from an app server). It does not look like a good thing for performance.
Yeah, but what are the odd that all of the servers are going to be down? In my case, it’s very unlikely. Also, I would expect and average of 1 callback per minute, based on what I know about our system. But your point is well taken. Personally, the most I’d wait is 2 seconds: thinking that if I don’t get a response after 2 seconds, it’s not going to happen. If a person was really concerned about performance then this would not be a good solution. Probably they would want to use dbms_jobs. What would you do?
Regards,
Mike
If I understand your code correctly, for each row update, you would have to wait for five seconds at worst or hundreds of milliseconds at best (time needed to get a page from an app server). It does not look like a good thing for performance.
Comment by VJ — June 14, 2007 @ 12:34 pm
Yeah, but what are the odd that all of the servers are going to be down? In my case, it’s very unlikely. Also, I would expect and average of 1 callback per minute, based on what I know about our system. But your point is well taken. Personally, the most I’d wait is 2 seconds: thinking that if I don’t get a response after 2 seconds, it’s not going to happen. If a person was really concerned about performance then this would not be a good solution. Probably they would want to use dbms_jobs. What would you do?
Regards,
Mike
Comment by Michael Moore — June 15, 2007 @ 4:57 pm