M
Mike Fechner
Guest
Hi Peter, this is really one of the cases where you should convince your client to introduce an AppServer. The AppServer allows much better to transmit parent/child record I a single ProDataset. Mike Von: willer [mailto:bounce-willer@community.progress.com] Gesendet: Mittwoch, 10. Dezember 2014 19:22 An: TU.OE.General@community.progress.com Betreff: [Technical Users - OE General] Client network performance with a join Client network performance with a join Thread created by willer Hello, still trying to get a bit faster. Everybody knows moving to a client network environment plugs in the tcp/ip layer between client and server. My analyzes shows that the prefetch mechanism works very fine and quite as fast as a local "tcp/ip" connection with -Mm 16384 on one table. In the following tests I select only 1280 records. The sample data contains for each customer exactly 357 bytes and every customer has one order record with 59 bytes. On a for each customer no-lock I get 547 tcp/ip packets with 515113 bytes transmitted. The time of 430 ms is relative here, as all tests were over a WLAN. Is O.K. On a for each oder no-lock I get 167 tcp/ip packets with 112600 bytes (time 100 ms). Now you guess, the for each customer no-lock, first order of customer no-lock transmits 5700 tcp/ip packets with 1517576 bytes (13500 ms). I see between each order a packet (268 bytes) which is processed at the server for about 3ms. Is it possible to explain what happens there and how to improve that. Or Is it possible to enhance the prefetch mechanism, that the client is sending requests disregarding server replies, and the server collects the request (prefetch) until a packet is filled up with requested data? Or do you have a solution how to select child table, when the primary table criteria is not possible to filter on child table? Thank you Regards Stop receiving emails on this subject. Flag this post as spam/abuse.
Continue reading...
Continue reading...