Due to bugs we've seen users with 10gb history files, which may
contribute to complaints.
http://code.google.com/p/chromium/issues/detail?id=24947
Even if compression ends up being pretty slow, you could imagine using
it for our archived history (history more than a month old).
On Tue, Nov 24,
On Tue, Nov 24, 2009 at 10:21 AM, Elliot Glaysher (Chromium)
wrote:
> I'm all for it. I vaguely remember people complaining about the size
> of our history files, and most of my history files are over 50M.
Part of the reason for this are bugs like
http://code.google.com/p/chromium/issues/detail?i
I'm all for it. I vaguely remember people complaining about the size
of our history files, and most of my history files are over 50M.
-- Elliot
On Tue, Nov 24, 2009 at 10:13 AM, Scott Hess wrote:
> Long ago when developing fts1, I experimented with using zlib
> compression as part of the impleme
Long ago when developing fts1, I experimented with using zlib
compression as part of the implementation. It fell by the wayside
because it really didn't provide enough performance improvement (I
needed an order of magnitude, it didn't provide it), and because of
licensing issues (fts1/2/3 are part
