I just did this and the web UI is much snappier.
I don't have a huge collection so I don't know if I'll see a big difference in scanning.
Thanks moonbase!
Results 51 to 60 of 93
-
2009-10-21, 23:15 #51Senior Member
- Join Date
- Jun 2009
- Location
- Kirkland, WA USA
- Posts
- 262
-Gordon
Squeezebox Server 7.53 + HP MediaSmart EX485
Duet/3 Receivers
Squeezeplay on all PCs
-
2009-10-21, 23:23 #52
-
2009-10-23, 10:24 #53
Haven't some of these tweaks to my.tt already made it into 7.4 as the 'stock' configuration? I thought I was seeing a difference between 7.3.4's my.tt and 7.4's.
-
2009-10-23, 10:42 #54Senior Member
- Join Date
- Apr 2005
- Location
- Colorado
- Posts
- 10,073
-
2009-10-23, 10:48 #55Senior Member
- Join Date
- Apr 2005
- Location
- Colorado
- Posts
- 10,073
The my.tt in 7.5 is the same as that of 7.4, while my.tt in 7.3 has a comment line that differs (the old server name) and the one from 7.2 is missing the tmpdir directive of later versions. Otherwise, all other configuration options are identical.
-
2009-10-23, 11:27 #56
Well, if you guys are confident that these changes work well with most hardware and don't introduce any instability, why not open an enhancement bug request? Writing a plugin to give users a gui for tweaking my.tt options seems a little like overkill to me. But a test script that would start & stop mysql with different 'tunings' and run timed test queries so as to affirm the efficacy of various options...now that I would like to see.
-
2009-10-23, 11:42 #57
its not overkill at all. many people like a gui b/c they don't feel confident messing around in the files, i know i don't. also a gui shows what "range" settings can be, allows for easy and quick changes to test different settings, and allows for some helpful explanatory text to give users pointers on what might work best on their kind of setup. (also allows "return to default")
besides, this kind of "tweaking" plugin could be extended to other tweaks in the future, not just moonbases excellent work here. i think its high time for an "under the hood" tweaking gui plugin.
-
2009-10-23, 12:58 #58
Dramatic speedup: Give database some room tobreathe
>its not overkill at all. many people like a gui b/c they don't feel
>confident messing around in the files, i know i don't. also a gui shows
>what "range" settings can be, allows for easy and quick changes to test
>different settings, and allows for some helpful explanatory text to give
>users pointers on what might work best on their kind of setup. (also
>allows "return to default")
No, it would be overkill. People who feel they need to tweak the database for extra speed should be aware of what they are doing. A GUI would allow too many people to tweak things that the ought not be touching.
-
2009-10-23, 13:08 #59
nonsense. you could say that about a TON of things already in SBS and the plugins. and besides, the plugin could clearly document things and make changes reversable.
too little faith is shown here in users, logitech suffers from "we know whats best" too much, and need to get over it. these are very substantial performance gains that should be put into easy configurable reach for those who look for it. big reward, little risk.
besides, i'm not advocating the plugin come with SBS by default, altho i'd have no beef with that, but it could be downloaded or what not. some other current plugins and abilities are in my opinon, far more complex to initiate and maintain then this would be.
-
2009-10-23, 13:53 #60
Dramatic speedup: Give database some room tobreathe
>nonsense. you could say that about a TON of things already in SBS and
>the plugins.
>
I can't think of any that modify the configuration of things that are outside the remits of the SbS software. Making such edits could potentially render the DB inoperable.
>too little faith is shown here in users, logitech suffers from "we know
>whats best" too much, and need to get over it.
>
It's dangerous to offer this to your average user via a plugin.
>these are very substantial performance gains that should be put into easy configurable
>reach for those who look for it. big reward, little risk.
>
Why should users need to configure the database? The DB could be auto-tuned at installation by the installer.
If users really want to optimise the DB further, they probably know what they are doing, or a tech-savvy enough to follow instructions to edit a text file.

Reply With Quote


