Mailinglist Archive: zypp-devel (115 mails)
| < Previous | Next > |
Re: [zypp-devel] Playing with sqlite cache
- From: "Duncan Mac-Vicar P." <dmacvicar@xxxxxxx>
- Date: Mon, 2 Jul 2007 11:40:59 +0200
- Message-id: <200707021140.59563.dmacvicar@xxxxxxx>
On Sunday 01 July 2007 09:23:20 pm Martin Schlander wrote:
> Den Sunday 01 July 2007 18:43:45 skrev Duncan Mac-Vicar P.:
> > You can see the curve has an optimum at 10 M or 15 M (is it worth to use
> > 5 mb to save 1 more second?)
>
> Speaking as a normal home user I'd say it's worth it. Think time is more
> valuable to most than an insignificant amount of disk space. Might be just
> 1 sec, but after all it's 4-5%
First: that is memory: it is the ram sqlite cache, not hard disk space. Sqlite
uses this to cache accessed pages.
I think you are missing one scenario: installation:
We could reduce a lot the time of writing the cache, without normalizing
names, that is what makes writing slow: we have to select each time before we
insert (well not really always, we have some memory caches), but this
increases your on-dik cache size by 3 mb per-factory repository: In order to
query FAST by names, you need an index, and if the columns are not
normalized, the index is big.
On installation, there is a ramdisk so everything you have on disk affects ram
usage.
Still, if we are not in installation, we could default to bigger ram caches,
or setup the value depending on the amoun of memory available.
You can see more numbers here:
http://en.opensuse.org/Libzypp/Refactoring/CacheSchema
Duncan
--
To unsubscribe, e-mail: zypp-devel+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: zypp-devel+help@xxxxxxxxxxxx
> Den Sunday 01 July 2007 18:43:45 skrev Duncan Mac-Vicar P.:
> > You can see the curve has an optimum at 10 M or 15 M (is it worth to use
> > 5 mb to save 1 more second?)
>
> Speaking as a normal home user I'd say it's worth it. Think time is more
> valuable to most than an insignificant amount of disk space. Might be just
> 1 sec, but after all it's 4-5%
First: that is memory: it is the ram sqlite cache, not hard disk space. Sqlite
uses this to cache accessed pages.
I think you are missing one scenario: installation:
We could reduce a lot the time of writing the cache, without normalizing
names, that is what makes writing slow: we have to select each time before we
insert (well not really always, we have some memory caches), but this
increases your on-dik cache size by 3 mb per-factory repository: In order to
query FAST by names, you need an index, and if the columns are not
normalized, the index is big.
On installation, there is a ramdisk so everything you have on disk affects ram
usage.
Still, if we are not in installation, we could default to bigger ram caches,
or setup the value depending on the amoun of memory available.
You can see more numbers here:
http://en.opensuse.org/Libzypp/Refactoring/CacheSchema
Duncan
--
To unsubscribe, e-mail: zypp-devel+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: zypp-devel+help@xxxxxxxxxxxx
| < Previous | Next > |