` Comment on an Icetips Article
Icetips - Templates, Tools & Utilities for Clarion Developers

Templates, Tools and Utilities
for Clarion Developers

Add a comment to an Icetips Article

Please add your comments to this article. Please note that you must provide both a name and a valid email address in order for us to publish your comment. Comments are moderated and are not visible until they have been approved. Spam is never approved!

Your Name:  
Email:  
Header text/Subject:  

Please enter your comment in the box below:

Back to article list   Search Articles     Add Comment     Printer friendly     Direct link  

Par2: FileBuffers for ASCII files
1998-11-02 -- John Longarrow
 
> Now, what I'm driving at is: Are there any rule of thumbs here to > calculate the size of the buffer size? And why this drastic > difference between the 16 and 32bit drivers? (Performance with buffers=5000 is worse in 32 bit than 16 bit and performance improves when buffers is set to 50; record length is 4096.) From what I understant, when you set FILEBUFFERS=5000 with a 4K record you are telling the driver to allocate 2 MEG per file to I/O buffering. With tiny files this is WAY overkill, and I'd say use DIRECTORY() to grab the file size. Then I'd SEND(FILEBUFFERS=(FileSize/RecordLength)) to the driver when accessing. I'm not sure if you can do this with the ASCII driver. If it doesn't, I'd play around with how many buffers to set based on expected file size. If you expect the files are going to be small, set a small number. Otherwise go with a big one. Then again, I think you alread demonstrated that!


Today is December 3, 2024, 11:56 am
This article has been viewed 35263 times.



Back to article list   Search Articles   Add Comment   Printer friendly

Login

User Name:

Password: