Open GoogleCodeExporter opened 9 years ago
Does this show up on some profiling that you've done? Would using fseeko bring
about a noticeable performance boost?
Original comment by dgrogan@chromium.org
on 29 May 2013 at 2:20
[deleted comment]
[deleted comment]
It doesn't show up in any profiling, nor is it a performance boost. I was just
reading the code and learning how it works when I saw that.
What I think might be a problem is that, as a "long" is only 4 bytes in a 32
bit machine, if the parameter "n" is greater than 2^31 (it is an uint64t_n), it
might wrap around
Original comment by guido.re...@yahoo.com
on 30 May 2013 at 5:56
Given how LevelDB works, it strikes me as unlikely that a 32-bit system would
end up having files large enough for -D_FILE_OFFSET_BITS=64 or fseeko to matter.
Original comment by cbsm...@gmail.com
on 4 Oct 2013 at 11:30
I think I've run into this issue. I'm doing a large batch import on a 64Bit
machine. This causes the log file to grow over 2GB. If I use this database on a
32Bit machine befor compaction has finished I get an error.
I'm interestd in a fix for this ;)
Original comment by ingemar....@philotech.de
on 2 Dec 2013 at 10:15
Original issue reported on code.google.com by
guido.re...@yahoo.com
on 29 May 2013 at 4:38