Project

General

Profile

Bug #2244

Performance bottle neck in Digir ProviderServlet

Added by Kevin Ruland almost 16 years ago. Updated almost 16 years ago.

Status:
Resolved
Priority:
Immediate
Assignee:
Category:
ecogrid
Target version:
Start date:
11/04/2005
Due date:
% Done:

0%

Estimated time:
Bugzilla-Id:
2244

Description

Now that each digir ecogrid query requests information from many different
providers (400 or so at any time), the performance of the Digir ProviderServlet
is a problem. In addition to the additional network hop between the ecogrid
DigirImpl and the Digir ProviderServlet, there are configuration issues in the
ProviderServlet itself.

A stopgap measure is to throttle back the Ecogrid DigirImpl service to accepting
a reduced number of simultaneous connections.

History

#1 Updated by Kevin Ruland almost 16 years ago

Fixed by creating a thread pool to manage connections to individual digir providers.

#2 Updated by Redmine Admin over 8 years ago

Original Bugzilla ID was 2244

Also available in: Atom PDF