Ticket #67 (new defect)

Opened 5 years ago

Last modified 5 years ago

Poor performance with larger data sets

Reported by: anonymous Assigned to: eitan
Priority: major Component: persistence
Version: Keywords:
Cc:

Description

using mytunes

1. create some fake mp3 files

e.g.

for(int i = 0; i < 1000; i++) {

(new File("c:/tmp/fake-" + i + ".mp3")).createNewFile()

}

2. right click on songs - click on 'Scan From Base Path'

3. select 'c:/tmp'

4. right click on songs - select 'browse'

  • there is a delay when opening this screen (2-5 seconds)

5. click on the left and right arrows to page between pages

  • there is a delay between screens of (1-3 seconds)

The database is a local instance of hsqldb the performance here is rather poor given the small data set (1000 documents)

Have not tested with a remote/heavier database database but the performance will only degrade further on either mysql/postgresql and god forbid oracle.

Change History

09/16/06 17:33:45 changed by anonymous

added another 1000 songs, and performance very poor (> 5 seconds between pages). Seems to degrade linearly as the number of records increases.

09/20/06 08:41:27 changed by anonymous

loaded a similar amount of objects and also getting a performance hit.

agree 1000 is not a big amount, especially when you're building crm/erp applications.

perhaps its hibernate/swing, from the list of other hibernate errors on this forum seems like it was a rather poor choice in terms of robustness. swing is also a problem, easily eating up 70mb after little usage or what seems to be rendering windows of trivial complexity, perhaps also an area to look into to improve performance

i suppose jmatter is more suited to small scale (less than 100 records per table) low volume, single user environments. at this point in time not sure what advantage it has over say a web based widget toolkit as you would expect a thick client application to be much faster than thin/web - sure, you get things like logging, search etc but nothing that can't be done if you application is broken down into reusable components.

interesting but, probably revisit this project after a year or two.

12/13/06 18:31:12 changed by eitan

  • component set to persistence.