[Yazlist] Performance tweaks for async. search?

Mike Taylor mike at indexdata.com
Thu Nov 29 17:24:09 CET 2007


Johannes Leveling writes:
 > Thanks for the quick response. I'm not quite sure IRSpy does what I
 > want (at least I didn't see it in the sources at first glance).
 > 
 > When the Zebra server logs this:
 > 17:29:35-28/11 zebrasrv(16) [request] Search Default OK 12553 1 1+21 RPN ... 
 > 17:29:42-28/11 zebrasrv(16) [request] Present Partial 2 -  1 22+79
 > 17:29:44-28/11 zebrasrv(16) [request] Present Partial 2 -  1 37+64
 > 17:29:47-28/11 zebrasrv(16) [request] Present Partial 2 -  1 50+51
 > ...
 > 17:29:56-28/11 zebrasrv(16) [request] Present OK -   1 91+10
 > 
 > My application receives the following ZOOM events (from connections to 2 
 > databases):
 > conn:2 last_ev:1 ZOOM_EVENT_CONNECT
 > conn:2 last_ev:6 ZOOM_EVENT_SEND_APDU
 > conn:2 last_ev:2 ZOOM_EVENT_SEND_DATA
 > conn:3 last_ev:1 ZOOM_EVENT_CONNECT
 > conn:3 last_ev:6 ZOOM_EVENT_SEND_APDU
 > conn:3 last_ev:2 ZOOM_EVENT_SEND_DATA
 > conn:3 last_ev:3 ZOOM_EVENT_RECV_DATA
 > conn:3 last_ev:7 ZOOM_EVENT_RECV_APDU
 > // conn: 3: 0 hits
 > conn:3 last_ev:6 ZOOM_EVENT_SEND_APDU
 > conn:3 last_ev:2 ZOOM_EVENT_SEND_DATA
 > conn:2 last_ev:3 ZOOM_EVENT_RECV_DATA
 > conn:2 last_ev:7 ZOOM_EVENT_RECV_APDU
 > // conn: 2: 0 hits
 > conn:2 last_ev:6 ZOOM_EVENT_SEND_APDU
 > conn:2 last_ev:2 ZOOM_EVENT_SEND_DATA
 > conn:3 last_ev:3 ZOOM_EVENT_RECV_DATA
 > conn:3 last_ev:3 ZOOM_EVENT_RECV_DATA
 > conn:3 last_ev:3 ZOOM_EVENT_RECV_DATA
 > conn:3 last_ev:3 ZOOM_EVENT_RECV_DATA
 > conn:3 last_ev:3 ZOOM_EVENT_RECV_DATA
 > conn:3 last_ev:3 ZOOM_EVENT_RECV_DATA
 > conn:3 last_ev:3 ZOOM_EVENT_RECV_DATA
 > conn:3 last_ev:3 ZOOM_EVENT_RECV_DATA
 > conn:3 last_ev:3 ZOOM_EVENT_RECV_DATA
 > conn:3 last_ev:3 ZOOM_EVENT_RECV_DATA
 > conn:3 last_ev:3 ZOOM_EVENT_RECV_DATA
 > conn:3 last_ev:7 ZOOM_EVENT_RECV_APDU
 > // conn: 3: 5281 hits
 > conn:2 last_ev:3 ZOOM_EVENT_RECV_DATA
 > conn:2 last_ev:7 ZOOM_EVENT_RECV_APDU
 > // conn: 2: 1564 hits
 > 
 > So, I want to start processing records at 
 > 17:29:35-28/11 (from the Zebra log), but records become available after
 > 17:29:56-28/11 (21 seconds later).

Er.  Now I'm lost.  You want to start processing the record before
you've retrieved them?  Asyncronous event handling won't help you with
that, you need a TARDIS!

Are you piggy-backing your searches so that the initial search
response includes some of the matching records?

 _/|_	 ___________________________________________________________________
/o ) \/  Mike Taylor    <mike at indexdata.com>    http://www.miketaylor.org.uk
)_v__/\  "... and that's why he's worth seven million pounds" -- Gary
	 Lineker on Andy Cole after a string of hopeless misses in a 0-0
	 draw vs Aston Villa.




More information about the Yazlist mailing list