Hi Boris,

... I've thought that it was meant that way :-)
It will be difficult even if hypothetically answer your question. If you have the problem only when I/O operations are executed, I will say there is something wrong?

I will try to spy a little with PEX. I don't know how the IFS files are implemented at the system level?
In WinX world, there are some parameters which give you more control over this operations, 'i' do not have that. Perhaps it could also answer the people of MI400 list.

I've only seen that depending on the open () parameters run per "write () " also matptr & xlateb and other operations ...
That would be the case when your writes to file with a different code page (hope so)?

Well, that theory is already too much :-)
Start PEX and maybe you'll find it.

Peter

-----Original Message-----
From: c400-l-bounces+peter.daransky=uc4.com@xxxxxxxxxxxx [mailto:c400-l-bounces+peter.daransky=uc4.com@xxxxxxxxxxxx] On Behalf Of Boris
Sent: Freitag, 27. Mai 2011 19:24
To: c400-l@xxxxxxxxxxxx
Subject: Re: [C400-L] Write to IFS file - high CPU

Peter,
I totally agree using memset in this case would the correct approach. I came to this sample program by simplifying my original program (that loop was formatting the buffer before it was sent to the output file) so guess I wasn't even concentrating on the loop but on the write function itself.

I guess my question is a hypothetical one...

Why does program that only uses an I/O function and does nothing but I/O consume so much CPU?

Boris.

--
This is the C programming iSeries / AS400 (C400-L) mailing list To post a message email: C400-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/c400-l
or email: C400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives at http://archive.midrange.com/c400-l.


This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2019 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available here. If you have questions about this, please contact [javascript protected email address].