On 4/23/12 9:42 PM, John Plevyak wrote:
Humm... it would be easy to enlarge the aggregation buffer or disable
the fragment offsets in the header. The former is probably the most
powerful solution since if you are serving huge documents, you
probably want the ability to restart/seek and likely also have
significant memory on a per disk basis. We could make it configurable.
Is this something we should add for v3.1.4 / v3.2?
Also, does increasing the fragment size change any of this ? Perhaps not
an ideal solution, but, we still haven't fixed TS-475 anyways so can't
position / seek afaik ?
-- Leif
CONFIG proxy.config.cache.target_fragment_size INT 1048576
