Buffer Explained?

For the other topic
Post Reply
sicktanick
Posts: 1
Joined: Sat Jan 16, 2016 12:26 am

Buffer Explained?

Post by sicktanick » Sat Jan 16, 2016 12:51 am

Greetings! I have the freeware version of this product and absolutely love it, I however am not super tech savvy so I was wondering if you could explain the buffer to me, what settings can I use to get the absolute fastest speed out of the software in combination with my cpu? Also what is the differerbe betwrrb the differebt algorithms and does that choice havr an imoact on the speed? have an i7 2600 . thank you!

User avatar
alpha_one_x86
Site Admin
Posts: 1246
Joined: Sun Oct 26, 2008 9:09 am
Contact:

Re: Buffer Explained?

Post by alpha_one_x86 » Sat Jan 16, 2016 1:00 am

From wikipedia:
In computer science, a data buffer (or just buffer) is a region of a physical memory storage used to temporarily store data while it is being moved from one place to another.

Typically, the data is stored in a buffer as it is retrieved from an input device (such as a microphone) or just before it is sent to an output device (such as speakers). However, a buffer may be used when moving data between processes within a computer. This is comparable to buffers in telecommunication. Buffers can be implemented in a fixed memory location in hardware—or by using a virtual data buffer in software, pointing at a location in the physical memory. In all cases, the data stored in a data buffer are stored on a physical storage medium. A majority of buffers are implemented in software, which typically use the faster RAM to store temporary data, due to the much faster access time compared with hard disk drives. Buffers are typically used when there is a difference between the rate at which data is received and the rate at which it can be processed, or in the case that these rates are variable, for example in a printer spooler or in online video streaming.

A buffer often adjusts timing by implementing a queue (or FIFO) algorithm in memory, simultaneously writing data into the queue at one rate and reading it at another rate.
If you wait the next version, the inode thread should be fonctionnal, and the version 2 will have async IO to improve the performance too.
Developer of ImageUltracopier/ImageSupercopier and of the game ImageCatchChallenger

Post Reply