search for: indexsize

...ta mostly from a project gutenberg dvd and other books, with relatively modest index sizes, from 1 to 24 GB. Quite curiously, in this zone, with all Xapian versions I tried, the ratio from index size to the amount of writes is roughly proportional to the index size to the power 1.5 TotalWrites / (IndexSize**1.5) ~= K So, not quadratic, which is good news. For big indexes, 1.5 is not so good but probably somewhat expected. The other good news is that the patch above decreases the amount of writing by a significant factor, around 4.5 for the biggest index I tried. The amount of writes is estimated w...

...034 "nv20_state_emit_framebuffer") at p_debug.c:335 #1 0xf76fe723 in nv20_state_emit_framebuffer (nv20=0x805ef68) at nv20_state_emit.c:139 #2 0xf76fef2e in nv20_emit_hw_state (nv20=0x805ef68) at nv20_state_emit.c:255 #3 0xf76ff70b in nv20_draw_elements (pipe=0x805ef68, indexBuffer=0x0, indexSize=0, prim=4, start=0, count=3) at nv20_vbo.c:20 #4 0xf76ff922 in nv20_draw_arrays (pipe=0x805ef68, prim=4, start=0, count=3) at nv20_vbo.c:73 #5 0xf7743ac8 in st_draw_vbo (ctx=0x8074d18, arrays=0x80ade38, prims=0x80ac994, nr_prims=1, ib=0x0, min_index=0, max_index=2) at state_tracker/st_draw.c:...

...dvd > and other books, with relatively modest index sizes, from 1 to 24 GB. > > Quite curiously, in this zone, with all Xapian versions I tried, the ratio > from index size to the amount of writes is roughly proportional to the index > size to the power 1.5 > > TotalWrites / (IndexSize**1.5) ~= K I could perhaps believe it would tend to O(n*log(n)) eventually due to the number of levels in the B-tree being log(n) (though the number of levels is bounded above by a fairly small constant so one could argue that's O(n)). But probably the merging on commit will actually determin...

...dvd > and other books, with relatively modest index sizes, from 1 to 24 GB. > > Quite curiously, in this zone, with all Xapian versions I tried, the ratio > from index size to the amount of writes is roughly proportional to the index > size to the power 1.5 > > TotalWrites / (IndexSize**1.5) ~= K > > So, not quadratic, which is good news. For big indexes, 1.5 is not so good > but probably somewhat expected. > > The other good news is that the patch above decreases the amount of writing > by a significant factor, around 4.5 for the biggest index I tried. >...

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

http://bugs.freedesktop.org/show_bug.cgi?id=23505 Summary: KDE's Kubrick has problems with xf86-video-nouveau driver Product: Mesa Version: git Platform: Other OS/Version: All Status: NEW Severity: normal Priority: medium Component: Drivers/DRI/nouveau AssignedTo: nouveau at

...nv50->screen->tesla; struct pipe_screen *pscreen = pipe->screen; void *map; + boolean ret; map = pipe_buffer_map(pscreen, indexBuffer, PIPE_BUFFER_USAGE_CPU_READ); @@ -254,23 +285,25 @@ nv50_draw_elements(struct pipe_context *pipe, OUT_RING (chan, nv50_prim(mode)); switch (indexSize) { case 1: - nv50_draw_elements_inline_u08(nv50, map, start, count); + ret = nv50_draw_elements_inline_u08(nv50, map, start, count); break; case 2: - nv50_draw_elements_inline_u16(nv50, map, start, count); + ret = nv50_draw_elements_inline_u16(nv50, map, start, count); break; case 4...