Displaying 4 results from an estimated 4 matches for "750228444".
2019 Jan 31
4
Amount of writes during index creation
...aster latest idxflushmb 200
1402524 1597352 0.96 1.14
2223076 3291588 0.99 1.48
2678404 4121024 0.94 1.54
3842372 7219404 0.96 1.88
4964132 10850844 0.98 2.19
6062204 14751196 0.99 2.43
19677680 125418760 1.44 6.37
xapian git master before patch idxflushmb 200
24707840 750228444 6.11 30.36
So that was 750 GB of writes for the big index before the patch...
As you can see my beautiful law does not hold so well for the biggest index :)
(K = 1.44)
It's not quite the same data though, so I would need more tests, but I
think I'll stop here...
The improvement brought...
2019 Feb 03
0
Amount of writes during index creation
...0.96 1.14
> 2223076 3291588 0.99 1.48
> 2678404 4121024 0.94 1.54
> 3842372 7219404 0.96 1.88
> 4964132 10850844 0.98 2.19
> 6062204 14751196 0.99 2.43
> 19677680 125418760 1.44 6.37
>
> xapian git master before patch idxflushmb 200
>
> 24707840 750228444 6.11 30.36
OK, so the patch makes a very significant difference here.
There are other changes between RELEASE/1.4 and master which will
likely affect improve indexing speed and memory use, but I'm not sure
there's anything which would affect disk writes (unless we end up
swapping to disk...
2019 Feb 02
0
Amount of writes during index creation
...> 1402524 1597352 0.96 1.14
> 2223076 3291588 0.99 1.48
> 2678404 4121024 0.94 1.54
> 3842372 7219404 0.96 1.88
> 4964132 10850844 0.98 2.19
> 6062204 14751196 0.99 2.43
> 19677680 125418760 1.44 6.37
>
> xapian git master before patch idxflushmb 200
>
> 24707840 750228444 6.11 30.36
>
> So that was 750 GB of writes for the big index before the patch...
>
> As you can see my beautiful law does not hold so well for the biggest index :)
> (K = 1.44)
> It's not quite the same data though, so I would need more tests, but I
> think I'll stop...
2019 Jan 21
2
Amount of writes during index creation
Hi,
I have had a problem report from a Recoll user about the amount of writes
during index creation.
https://opensourceprojects.eu/p/recoll1/tickets/67/
The issue is that the index is on SSD and that the amount of writes is
significant compared to the SSD life expectancy (index size > 250 GB).
>From the numbers he supplied, it seems to me that the total amount of block
writes is roughly