Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[kaspiterina]

I would like if you could add the option to set the buffer size more then 2,5 MB, for example 10Mb or more for file and the option to set the buffer time limit more then 1 minute ( 60 for example)
thank you
bye

[lfroen]

I can't even imagine why this particular number (2.5Mb) bothers you. Care to explain? About time limit - can you explain what are you talking about?

[moron]

A small file buffer size stresses the harddisk needlessly. I would also prefer a free scaling. Actually it is only implemented as a percentage of 1,5MB. It is not possible to set it to any value above 1,5MB.

Buffer time limit means that the buffer is flushed to harddisk after a certain period of time regardless if the buffer size limit is reached or not. this function is not implemented in amule.

Low file buffer sizes are used to prevent data loss in case of a crash. data amounts and bandwiths have increased tremendously. The buffer sizes used in amule are not comparative anymore.

Anyways the health of my harddisk is way more woth than a few MB's of transferred data.

[lfroen]

A small file buffer size stresses the harddisk needlessly. I would also prefer a free scaling.

Wrong.

Buffer time limit means that the buffer is flushed to harddisk after a certain period of time regardless if the buffer size limit is reached or not. this function is not implemented in amule.

And it's OK. aMule writes to disk every time it has data. This is how application (any application) is supposed to work. Buffering/caching is job of OS and/or disk controller.

Anyways the health of my harddisk is way more woth than a few MB's of transferred data.

health of your harddisk have nothing to do with amount of data aMule transfer.

[moron]

A small file buffer size stresses the harddisk needlessly. I would also prefer a free scaling.

Wrong.

Wrong.

Buffer time limit means that the buffer is flushed to harddisk after a certain period of time regardless if the buffer size limit is reached or not. this function is not implemented in amule.

And it's OK. aMule writes to disk every time it has data. This is how application (any application) is supposed to work. Buffering/caching is job of OS and/or disk controller.

amule is an application which has its focus on data exchange.  Thats why amule's access to data is not comparable with usual application's data access. And that is why data caching is part of amule and that is why data caching is useful and  important. Caching can be the job of the OS and in most cases the OS does some optimizings for data flow. But it is not necessarily  sufficient and optimal.

Anyways the health of my harddisk is way more woth than a few MB's of transferred data.

health of your harddisk have nothing to do with amount of data aMule transfer.

considering the things i mentioned above, it has to do with each other.

[lfroen]

A small file buffer size stresses the harddisk needlessly. I would also prefer a free scaling.

Wrong.

Wrong.

OK, nothing to see here, moving on.

amule is an application which has its focus on data exchange.  Thats why amule's access to data is not comparable with usual application's data access. And that is why data caching is part of amule and that is why data caching is useful and  important. Caching can be the job of the OS and in most cases the OS does some optimizings for data flow. But it is not necessarily  sufficient and optimal.

Did you care to check the facts first? No offense, but you seem completely clueless regarding how OS and disk actually works when it comes to file access. What you suggesting here is simply wrong.

Anyways the health of my harddisk is way more woth than a few MB's of transferred data.

considering the things i mentioned above, it has to do with each other.

Please, do a favor - check google about "harddisk MTBF" before starting such discussion. You will save lot of time, and will educate yourself about many things.