Displaying 4 results from an estimated 4 matches for "6123140".
2019 Jan 31
4
Amount of writes during index creation
...s estimated with iostat before/after. The disk has
nothing else to do.
idxflushmb is the number of megabytes of input text between Xapian commits.
xapiandb,kb writes,kb K*1000 sz/w
xapian 1.4.5 idxflushmb 200
1544724 6941286 3.62 4.49
3080540 16312960 3.02 5.30
4606060 21054756 2.13 4.57
6123140 33914344 2.24 5.54
7631788 50452348 2.39 6.61
xapian git master 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....
2019 Feb 03
0
Amount of writes during index creation
...apiandb,kb writes,kb K*1000 sz/w
>
> xapian 1.4.5 idxflushmb 200
If you're going to the trouble of profiling, probably best to use the
latest release (1.4.5 was released in 2017).
> 1544724 6941286 3.62 4.49
> 3080540 16312960 3.02 5.30
> 4606060 21054756 2.13 4.57
> 6123140 33914344 2.24 5.54
> 7631788 50452348 2.39 6.61
>
> xapian git master 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
> 60622...
2019 Feb 02
0
Amount of writes during index creation
...t; nothing else to do.
>
> idxflushmb is the number of megabytes of input text between Xapian commits.
>
> xapiandb,kb writes,kb K*1000 sz/w
>
> xapian 1.4.5 idxflushmb 200
>
> 1544724 6941286 3.62 4.49
> 3080540 16312960 3.02 5.30
> 4606060 21054756 2.13 4.57
> 6123140 33914344 2.24 5.54
> 7631788 50452348 2.39 6.61
>
> xapian git master 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
>...
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