Arvid Norberg comments

Results 1037 comments of


                                            Arvid Norberg

docs:disk_interface::[async_move_storage()]

> It's not even about parts or not parts. My paragraph that you quoted was in response to question (1), not (2). It was not about turning an allocated file...

RC_2_0: Write cache doesn't flush to disk

stopping the torrent will cause libtorrent to close the files (and file maps), which it sounds like will also trigger windows to flush the dirty pages. This seems to be...

RC_2_0: Write cache doesn't flush to disk

It seems like the most appropriate fix is to schedule a call to FlushViewOfFile() periodically

RC_2_0: Write cache doesn't flush to disk

actually, every time a file completes, its file handle is closed. I believe this will flush it to disk. This is primarily to make sure the next time it's accessed...

RC_2_0: Write cache doesn't flush to disk

From the `FlushViewOfFile()` documentation: > Flushing a range of a mapped view **initiates** writing of dirty pages within that range to the disk. [...] The FlushViewOfFile function does not flush...

RC_2_0: Write cache doesn't flush to disk

Here's a start of a fix: https://github.com/arvidn/libtorrent/pull/6529

RC_2_0: Write cache doesn't flush to disk

I don't think this is just an issue in old versions of windows. as far as I know, all versions of windows have issues balancing disk cache against, for example,...

RC_2_0: Write cache doesn't flush to disk

There is this call already, does that do what you need? http://libtorrent.org/reference-Torrent_Handle.html#flush-cache

RC_2_0: Write cache doesn't flush to disk

yes, I agree that libtorrent probably doesn't implement the documented behavior currently.

RC_2_0: Write cache doesn't flush to disk

> What if I don’t like the kernal allowing one app to use almost all the RAM. Technically, it's not the program using the RAM, it's the kernel using it...