java - Why do multiple RPC calls in GWT significantly slow response time? -
i'm testing google web toolkit application , having performance issue multiple rpc calls. structure of app is:
- user submits query
- initial query serviced single server-side servlet
- once initial reply received, multiple components subsequently updated iterating on each component , calling update method, passing results of initial query
- each component's update method work on data passed it, in addition potentially calling other server-side services
- on success of these calls, component updated in ui.
with initial query service , 1 component (effectively running sequentially), response time fast. however, adding other components (e.g initial query service + 2 components, these 2 components calling asynchronously) hugely impacts response time.
is there way improve / rectify this?
example: (iqs = initial query, c1 = component 1, c2 = component 2, c1s = comp. 1 service, c2s = component 2 service)
initial query + 1 component iqs, returned - propagating results, 1297273015477 c1, sending server request,1297273015477 c1s, sending back..., 1297273016486 c1, receiving complete, 1297273016522 (total time initial call - 1045ms) initial query + 2 components iqs, returned - propagating results, 1297272667185 c1, sending server request,1297272667185 c2, sending server request,1297272668132 c1s, sending back..., 1297272668723 c2s, sending back..., 1297272669371 c1, @ client process, 1297272671077 (total time initial call - 3892ms) c2, @ client process, 1297272674518 (total time initial call - 6386ms)
thanks in advance.
paul
i think need make analysis more fine grained: in data provided have established client started 2nd component call , got response 6386ms later. of was
- going on wire
- being received @ server
- processed @ server (this broken down, well).
- sent on wire.
the gwt-rpc service has 1 , 4. know how long each step takes?
Comments
Post a Comment