Hi!
Ralph Glasstetter wrote:
PS: Has disabling the mmap part under windows any disadvantages?
I'm not sure if mmap ever had any advantages on Windows at all, compared
to read.
On Linux/Unix, I would claim that mmap is a little faster (but not
much). On Windows, the difference in performance
Hi!
I wrote:
posix_fadvise(), on the other hand, is something we could try as well.
In particular, the POSIX_FADV_DONTNEED flag might be useful in the
(sequential) indexing and export phases.
And the results are: 30-40% faster indexing, 10-20% faster export.
Not bad for a rather simple
Hi,
And the results are: 30-40% faster indexing, 10-20% faster export.
Cool,... does it also affect the Windows port?
I saw no #ifndef WIN32...
Anyway,... just tried to compile REV53 on Windows and the new makefile
saved a lot of time by compiling just the few updated files. :-))
However,
Hi!
Ralph Glasstetter wrote:
And the results are: 30-40% faster indexing, 10-20% faster export.
Cool,... does it also affect the Windows port?
I saw no #ifndef WIN32...
That's implied. :-)
Windows does not define POSIX_MADV_DONTNEED, so the interesting part
which calls posix_fadvise()
Hi!
Ralph Glasstetter wrote:
However, when I tried to build from a fresh SVN checkout it still did not work
because of missing dvbcutbase.h and colleagues...
Fixed in r54.
--
Michael Tired Riepe [EMAIL PROTECTED]
X-Tired: Each morning I get up I die a little
Hi!
Seems like dvbcut works on Windows again. At least the files it produces
are bitwise identical to those written by the Linux versions (both index
and export files). I only had to turn off mmap() on Windows. If you look
at the implementation (found in dvbcut/import/sys/mman.h), you will
:31
An: discussions and announcements dvbcut-user@lists.sourceforge.net
Betreff: [DVBCUT-user] Revision 52 -or- Windows works again
Hi!
Seems like dvbcut works on Windows again. At least the files it produces
are bitwise identical to those written by the Linux versions (both index
