Bug 16460 – Scanning with MySQL is very slow

Bug 16460 - Scanning with MySQL is very slow

Summary:

Scanning with MySQL is very slow

Status:	RESOLVED INVALID

Product:	Logitech Media Server
Classification:	Unclassified
Component:	Scanner
Version:	7.6.0
Platform:	PC Windows 7

Importance:	P2 normal with 1 vote (vote)
Target Milestone:	Future
Assigned To:	Andy Grundman

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2010-08-14 02:21 UTC by michael123
Modified:	2014-08-06 10:22 UTC (History)
CC List:	2 users (show)

See Also:
Category:	---

Attachments
Info (27.23 KB, image/png) 2010-08-14 02:21 UTC, michael123	Details
FUll Scan using SQLite (23.46 KB, image/png) 2010-08-14 07:12 UTC, michael123	Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description michael123 2010-08-14 02:21:14 UTC

Created attachment 6932 [details]
Info

Which is more than 3 times worse in 7.5.1 (it was 45 minutes)..

I use MySQL

see attached

Comment 1 michael123 2010-08-14 07:12:56 UTC

Created attachment 6933 [details]
FUll Scan using SQLite

Comment 2 michael123 2010-08-14 07:15:17 UTC

When I switched to SQLite, it took now 40 minutes (see 2nd attachment)

I run Squeezebox on Lenovo X201 laptop (Core i5, 4GB RAM, 320GB 7200rpm), Lime unRAID NAS over Gigabit network

Due to new bug with UNC paths in version 7.6, I access using share mapping.

Comment 3 Mike Walsh 2011-01-14 10:12:10 UTC

do you have high performance enabled?  meaning, you have extra ram?

Comment 4 michael123 2011-01-14 10:38:45 UTC

(In reply to comment #3)
> do you have high performance enabled?  meaning, you have extra ram?

You mean 'Database Memory Config'?
Yes, it is set to 'High', 
but since I opened the bug, I switched to SQLite.

Should I re-test with MySQL?
Do you claim that performance of MySQL and SQLite is not same?