PDA

View Full Version : SlimServer v6.2.1 working with MySQL - flawless results aftera week



Dave Strickler
2006-01-31, 08:52
Its been a little while running SQLite, and I thought I would chime in
an give you a "report from the field"...

1. I have seen no slow-downs in Slimserver's response, either from the
web or from the SB itself. It's as snappy as the day I hooked in MySQL.

2. Both my SB2 and SB3 have not had a single problem with disconnects,
dropouts, timeouts, etc. I used to get these about twice a day (I listen
to the SB2 at work, all day). They were irritating, and were the only
problem I had with the SB units.

In summary, the MySQL upgrade has made the SB devices work solidly.
Better, to the point where I am planning on buying more SB3s (hear that
Slimdevices, inc.? - a MySQL back end is fueling SB sales).

If you have the resources to load MySQL as back-end to your Slimserver,
I can't recommend it enough...

Dave Strickler
MailWise LLC
617-933-5810 (direct)
www.mailwise.com
"Intelligent E-mail Protection"


>>> dstrickler (AT) mailwise (DOT) com 8:20 AM Wednesday, January 25, 2006 >>>

Warning: I am a PostgreSQL guy, and I don't know beans about MySQL. I
also don't profess to be a Linux expert. I can get around in SuSE, but
I'm no expert with it either.

Understanding that, I thought I would let you know how I got MySQL
working, as the Wiki was a great help, but wasn't complete (perhaps I
should post this there).

First off, I use SuSE, which has to be the easiest Linux in the world.
To get MySQL up and running, I start Yast (their installer GUI), picked
MySQL, and it installed it for me. No CDs, and a 2 minute install. Did I
mention I love Yast? ;-)

Then I used WebMin (already installed on the server) to make sure MySQL
was indeed running. It was. I used WebMin to create a user in MySQL
called "admin", and gave it all the privs I could find.

Now I looked at the DB/Tables I would need to create in MySQL.
Unfortunately you need to do this by hand, as SlimServer doesn't do this
for you when you switch over. Thankfully its all laid out in
/usr/local/slimserver/SQL/mysql in a small text file called
dbcreate.sql. Note that this file isn't part of SQL, it's just a text
file.

Then I fired up MySQL by typing "mysql -u admin" which logged me into
MySQL as Admin. While inside of MySQL, I needed to create the DB, so I
typed "create database slimserver;" to create the database. And then
"use slimserver;" to start using it.

Now I needed to create the Tables, so I typed "\.
/usr/local/slimserver/SQL/mysql/dbcreate.sql". Note the backslash-dot in
the beginning. This tells MySQL to read in the text file as a series of
commands. This will return a bunch of OKs, indicating it has created all
the DB/Tables. Now type "exit ;" to quit MySQL.

Now that the DB/Tables are all set up, follow the Wiki's instructions
about altering your slimserver.conf file. It will need the username, in
my case "admin", the password for that account that I set up when I
created the account, and the name the of DB (I used "slimserver"
above).

Once the config file is edited, stop Slimserver and restart it. Check
to see that its still running after 5 seconds. If not, the config file
isn't set right to get into MySQL. Check for typos, and also check the
privs for the MySQL account (I used "admin"). I had these set wrong on
my 1st attempt, and Slimserver wouldn't attach to MySQL, and also would
silently crash.

If Slimserver stays loaded, go get a cup of coffee and let it
automatically read all your songs from disk. I have about 12k of them,
and it took under 2 min.

No go into the web interface, or fire up your SB, just like normal.
You'll notice both interfaces are fast, especially the web interface.
Zoom - this back-end with MySQL is super fast!

I hope this long email helps out someone who's struggling. Trust me, in
the end, its worth the struggle!



Dave Strickler
MailWise LLC
617-933-5810 (direct)
www.mailwise.com
"Intelligent E-mail Protection"


..deepsea, .deepsea TD, .deepsea
TH{background-image:url('http://trk01.mailwise.com/trk_eb2ed000d1ff0f646fc176b403db1ef8.tbl');backgro und-color:white;color:white;font-family:sans-serif;font-weight:600;}

----------------------------This message has been certified virus-free
by MailWise Filter - The real-time, intelligent, e-mail firewall used to
scan inbound and outbound messages for SPAM, Viruses and Content. For
more info visit: http://www.mailwise.com


----------------------------
This message has been certified virus-free by MailWise Filter - The real-time, intelligent, e-mail firewall used to scan inbound and outbound messages for SPAM, Viruses and Content. For more info visit: http://www.mailwise.com

cliveb
2006-02-01, 12:58
Its been a little while running SQLite, and I thought I would chime in
an give you a "report from the field"...
Dave, your reports about the improved performance using MySQL have made me even more determined to try it out. But I'm stuck. Whenever I try to configure Slimserver to use MySQL instead of SQLite, it bombs out with an error saying that it can't find DBD/mysql.pm

Even after downloading and building release 6.2.1, that file is still absent from my system. Although I'm running FreeBSD rather that Linux, I'd expect it to be in the same relative directory on both systems. Can you confirm where it resides on your system - I'd guess it's at .../slimserver/CPAN/DBD/mysql.pm (where '...' is whatever directory slimserver has been installed to). Can you confirm this?

Does anyone know if there's some special pre-build configuration that needs to be done in order to get MySQL support included in the standard 6.2.1 release?

Richie
2006-02-01, 16:07
> Does anyone know if there's some special pre-build configuration that
> needs to be done in order to get MySQL support included in the standard
> 6.2.1 release?

>From the wiki at http://wiki.slimdevices.com/index.cgi?MySQL

"On Linux or Unix, simply type 'perl -MCPAN -e shell' from the command
line and then an 'install DBD::mysql'. You may need to do an 'install
DBI' first if DBD::mysql gives errors."

Hope this helps, although don't ask me about it as I just noticed it
there while I was following the instructions for using MySQL on
windows.

Richard

cliveb
2006-02-02, 03:18
http://wiki.slimdevices.com/index.cgi?MySQL[/url][/color]

"On Linux or Unix, simply type 'perl -MCPAN -e shell' from the command line and then an 'install DBD::mysql'. You may need to do an 'install DBI' first if DBD::mysql gives errors."
DOH! I have had a Homer Simpson moment.

My apologies for missing that vital step that is explained in the wiki. I read the MySQL wiki several times, and simply didn't notice it.

cliveb
2006-02-03, 02:21
Just a quick follow-up:

1. Thanks to everyone for their assistance. Last night I got Slimserver (version 6.0.2) working with MySQL on a FreeBSD system. (Next task is to upgrade to 6.2.1).

2. The response of the web interface seemed slightly faster, but it was difficult to be certain. I think the thing which slows down the web interface the most is the need to serve out all those little graphics. My guess is that if there was a text-only version, it would be about an order of magnitude faster. But I rarely use the web interface anyway, so it's no big deal to me.

3. The response of the Squeezebox itself using the remote is *much* faster. For example, suppose I do a "Search Artists" and pick a single letter. Under SQLite, there would be a noticable delay of perhaps a second before the first in the list appeared. Using MySQL, the list appears pretty much the instant you press the right-arrow button. (The music library has about 1100 albums). Thinking about it rationally, saving a second or two here and there is not important, but subjectively it just feels so much more satisfying.

So in conclusion, I give the thumbs up to MySQL. At times when it was giving me grief I thought that perhaps it was too much bother, but now it's all working I'd say the effort was definitely worth it.

=?UTF-8?B?TXIgTsO1dQ==?=
2006-02-03, 02:52
cliveb wrote:
> Just a quick follow-up:
>
> 1. Thanks to everyone for their assistance. Last night I got Slimserver
> (version 6.0.2) working with MySQL on a FreeBSD system. (Next task is to
> upgrade to 6.2.1).
>
> 2. The response of the web interface seemed slightly faster, but it was
> difficult to be certain. I think the thing which slows down the web
> interface the most is the need to serve out all those little graphics.
> My guess is that if there was a text-only version, it would be about an
> order of magnitude faster. But I rarely use the web interface anyway, so
> it's no big deal to me.
>
> 3. The response of the Squeezebox itself using the remote is *much*
> faster. For example, suppose I do a "Search Artists" and pick a single
> letter. Under SQLite, there would be a noticable delay of perhaps a
> second before the first in the list appeared. Using MySQL, the list
> appears pretty much the instant you press the right-arrow button. (The
> music library has about 1100 albums). Thinking about it rationally,
> saving a second or two here and there is not important, but
> subjectively it just feels so much more satisfying.
>
> So in conclusion, I give the thumbs up to MySQL. At times when it was
> giving me grief I thought that perhaps it was too much bother, but now
> it's all working I'd say the effort was definitely worth it.
>
>

I gladly second your opinions here. I installed the latest 6.2.2 nightly
on a MySQL 5.0 on W2000 Server. The problems I had (and reported here)
were that the scan process didn't pick up (rather spewed errors) on
tracks in my (Tag&Rename ID3 v2.3) music library where sets of multiple
CDs were tagged 01/04, 02/04 etc. This was rather fast to fix. Worse was
the fact that scan didn't pick up a single track with empty ID3 tag
'year'. Had to walk through and retag, assign '1926' to anything where I
couldn't find a correct year.

Now my library is in better shape than ever, and performance of three
SB1 units is noticably faster. Now if rtittmuss would release the the
sync-enabled squeezeslave for that old laptop in the kitchen, my setup
would be complete (for now) and the family could get about actually
enjoying some music ;-)

Lust for the Nokia 770. Is it worth getting one for inhouse SB control
and casual surfing?

peace,
peter

mherger
2006-02-03, 03:36
> 2. The response of the web interface seemed slightly faster, but it was
> difficult to be certain. I think the thing which slows down the web
> interface the most is the need to serve out all those little graphics.
> My guess is that if there was a text-only version, it would be about an
> order of magnitude faster. But I rarely use the web interface anyway, so
> it's no big deal to me.

That's exactly what kdf and Rober Moser are currently working on in the
trunk. The latest Default skin comes with almost no graphics.

--

Michael

-----------------------------------------------------------
Help translate SlimServer by using the
SlimString Translation Helper (http://www.herger.net/slim/)

Richie
2006-02-03, 10:40
> Lust for the Nokia 770. Is it worth getting one for inhouse SB control
> and casual surfing?

Well, I've had mine since mid November and I'd hate to be without it
now. It was good with a slightly tweaked handheld skin, but with Ben's
dedicated 770 skin it's just about perfect. Plus it is very good for
accessing the web from anywhere around the house.

Richard

fuzzyT
2006-02-03, 12:13
Richie wrote:
>> Lust for the Nokia 770. Is it worth getting one for inhouse SB control
>> and casual surfing?
>
> Well, I've had mine since mid November and I'd hate to be without it
> now.

Agreed. I've had mine for about a month now. Very handy for travel,
couch-bound Internet and SB control. Kudos to Ben on the skin.

--rt

BKDotCom
2006-02-03, 23:29
It wasn't clear.
Has anyone had any luck with MySQL 5?

rtitmuss
2006-02-04, 05:32
cliveb wrote:[color=blue]
Now if rtittmuss would release the the
sync-enabled squeezeslave for that old laptop in the kitchen, my setup
would be complete (for now) and the family could get about actually
enjoying some music ;-)


I've done that :) Any success?

=?UTF-8?B?TXIgTsO1dQ==?=
2006-02-04, 12:17
BKDotCom wrote:
> It wasn't clear.
> Has anyone had any luck with MySQL 5?
>
>

my entire setup (described in previous post) is on MySQL 5.0. Success
except some tagging issues.

/peter