in my exp, it is not a placebo effect. i noticed a big difference both
in faster scanning, and responsiveness. i mean, there is no question
in my mind that artwork loaded faster in the webui, clicks were quickly
responded to, etc.
a third option where mem allocation equals DB size sounds good
Further observations.
Squeezebox.db - 276,247Kb, Cache Size and Default cache size set to
300,000. Library 107,781 tracks, 9273 albums, 3420 artists. WIN XP SP3,
4Gb Ram, E5200 dual core @ 2.5GHz. SBS Version: 7.6.0 - r31275
Ran a Look for new changed music scan, browsed by Artists, Albums
and
whether it is MySQL or SQLite, it seems to me that all the settings
would be best set by some kind of auto tuner. surely there is some
script out there that could benchmark your cpu, ram, hard disk speeds,
and so on and then take into account your library size, art settings,
etc... and determine
andyg;571278 Wrote:
On Aug 22, 2010, at 7:47 PM, copperstate wrote:
Setting the Performance/Database Memory Config entry to High
whilst
using MySQL does not work:
Oops, I forgot to check the file in. :)
andyg, is this in yet? Does it make a permanent change or just set
these
On Aug 31, 2010, at 7:46 PM, Wirrunna wrote:
andyg;571278 Wrote:
On Aug 22, 2010, at 7:47 PM, copperstate wrote:
Setting the Performance/Database Memory Config entry to High
whilst
using MySQL does not work:
Oops, I forgot to check the file in. :)
andyg, is this in yet? Does it
I just enabled this in 7.6.0 running on Windows Server 2003 and the
memory usage of the server goes up significantly (then plateaus) as you
browse around Albums. Memory usage for the 7.6.0 himem server is about
126 MB, while a comparably configured 7.5.2 server using MySQL is at
101 MB.
I can't
On Aug 31, 2010, at 8:19 PM, JJZolx wrote:
I just enabled this in 7.6.0 running on Windows Server 2003 and the
memory usage of the server goes up significantly (then plateaus) as you
browse around Albums. Memory usage for the 7.6.0 himem server is about
126 MB, while a comparably
andyg;573494 Wrote:
It's not permanent in the database, but only at runtime, i.e. the
pragmas are set every time you start the server.
andyg, thank you for that explanation.
A bit of experimenting showed that if a user wants SBS to use
unnecessarily large amounts of memory then do NOT set
I checked out 7.6 31254 and had a go with the dbhighmem setting.
Searches are much quicker, and so far my SliMP3 hasn't glitched when I
search during playback. I'm using SQLite.
Colour me happy.
--
pallfreeman
They only want you when you're seventeen,
When you're twenty one, you're no fun.
Couldn't resist trying this out.
Ran a clear rescan on my workstation, then set cache size to 10
(andyg is always conservative with his settings) and ran the clear and
rescan again for a 16 minute reduction in elapsed time. Cut paste
attached. Win XP.
A google for SQLite optimization
Yep there be settings soon, they are in the 7.6 onebrowser branch .
Maybe soon they are in the 7.6 beta ? then I try :)
--
Mnyb
Main hifi: Touch + CIA PS +MeridianG68J MeridianHD621 and assorted amps
SiriuS, Classe' Primare
On Aug 22, 2010, at 4:37 AM, Wirrunna wrote:
Couldn't resist trying this out.
Ran a clear rescan on my workstation, then set cache size to 10
(andyg is always conservative with his settings) and ran the clear and
rescan again for a 16 minute reduction in elapsed time. Cut paste
Wirrunna;571043 Wrote:
Couldn't resist trying this out.
Ran a clear rescan on my workstation, then set cache size to 10
(andyg is always conservative with his settings) and ran the clear and
rescan again for a 16 minute reduction in elapsed time. Cut paste
attached. Win XP.
A google
andyg; Wrote:
Default pragmas are:
PRAGMA synchronous = OFF
PRAGMA journal_mode = MEMORY
PRAGMA foreign_keys = ON
PRAGMA locking_mode = EXCLUSIVE
With the highmem pref enabled you also get:
PRAGMA cache_size = 2 (default is 2000)
PRAGMA temp_store = MEMORY
Andyg, thank you
Setting the Performance/Database Memory Config entry to High whilst
using MySQL does not work:
Code:
[10-08-23 01:28:12.4623] Slim::Utils::MySQLHelper::createConfig (177)
Warning: Couldn't open
On Aug 22, 2010, at 7:47 PM, copperstate wrote:
Setting the Performance/Database Memory Config entry to High whilst
using MySQL does not work:
Oops, I forgot to check the file in. :)
___
beta mailing list
beta@lists.slimdevices.com
Mnyb;570748 Wrote:
Can increased performance be a setting in sbs ?
I bet there are other parameters too :)
Squeezebox Server Enterprise Edition: cache everything you can,
multithreaded to use multiple CPUs, scan several files from the library
at once to make use of those RAIDs...
I wish I
andyg;570141 Wrote:
SQLite has parameters to keep more of the database in memory, if you
want to use the CLI you can set them
That's pretty much exactly what I wanted. Thanks!
--
pallfreeman
pallfreeman's Profile:
How do I use this info practically, my server does nothing but sbs and
have 1gB of ram running rpm linux, thanks .
CLI huh ?
I suppose I just can't type pragma cache_size=1 at any shell and
be hapy :)
Id love to have sbs use more of my ram say 512mB if it would make it
faster
This is not
All I can say is read the docs and experiment, I haven't played with these
settings myself. CLI is:
telnet server 9090
Also note that you'll probably have to apply these every time you restart SBS,
although some may be saved in the database itself. I will also probably add a
way to get the
Ok telnet, will try there is a default cache size too
--
Mnyb
Main hifi: Touch + CIA PS +MeridianG68J MeridianHD621 and assorted amps
SiriuS, Classe' Primare and Dynadio speakers, Contour 4 Contour Center,
and Contour
SQLite has parameters to keep more of the database in memory, if you
want to use the CLI you can set them:
Docs here: http://www.sqlite.org/pragma.html
To set a pragma over CLI just run: pragma cache_size=1
--
andyg
My server is currently at 102MB for 7.5.2 and 94MB for 7.6.0. MySQL is
stretchin' out at 252 MB. :) I have most of the default plugins
disabled on both servers and no third party plugins installed. I think
I've only seen memory usage above 120 MB when there's either a memory
leak in the main
23 matches
Mail list logo
