Pavel Ilyashenko wrote:
Hi,
There are two questions:
1. In run-time we see that the process spends ~20% in system call - read.
Also we see that the reading of verified XML files is performed with buffer
size 508b.
turss command output:
open("/spotuser/nft/aimsys/nftwrk83/var/m3g/projs/dd/temp/Dec/23/dd.ABL_Statement_XML0000032373A00412007020000000003.200712230712231130.temp.xml",
O_RDONLY|0x800, 0666) = 51
read(51, "< s t a t e m e n t > \n< b i l ".., 512) = 512
read(51, "a n c e - c e n t e r > < r e m ".., 508) = 508
read(51, "t e m e n t - a d d r e s s - p ".., 508) = 508
read(51, "m i d d l e - n a m e > S E E D ".., 508) = 508
Actually, we harden to understand how is the buffer size defined?
Do you have any idea what may be a cause?
Perhaps this is the default buffer size for the open() system call on your OS.
2. Do you have any recommendation/reference list of performance issue which we
can use in order to improve your API usage?
Not that I know of. Perhaps you can call some system-specific API to
increase or decrease the buffer size to see how that affects performance.
Dave
