Many Players makes TD3 Slow

[peterw]

G'Day,

I've installed the TD3.1.1 and all is going well until I import the players to the database.
The CSV has 6743 records.  Now when I attempt to add Players Add to the Tournament or Search via the Find process the Player Buy-In process is very slow. 

(15 seconds to initially show the list of players in the League before the prompt to find is able to be used.)
(50 seconds to find the player.  We have unique ID cards with a Barcode to identify the player which is in the ID field. However it does not seem to matter if this ID is used or if the searching via Player name)

The Laptop PC's I have is the latest models Intel i5 with 4GB RAM and in all other functions very quick. 

Do you have any ideas on what could be wrong or done to improve this?

Kind Regards

[jodybingo]

I have the same issue (had). My DB had over 8000 names. my solution was to work from the database tab. Click Find Player and scan. The result is returned very fast.

[Corey Cooper]

Not surprising.  It's just a sign of the limitations of the framework.  The TD runs inside of Internet Explorer, primarily using Javascript.  There's been a lot of development in Microsoft's JScript implementation of Javascript, and the TD has benefited a lot from it, but it's still an interpreted language and has to rely on the rendering engine of IE (which is hugely flexible, but at a cost of speed in certain circumstances).  Over the years I have made a lot of improvements to speed up the application for situations like this, but there's only so much that can be done.

Even so, I think there is something else at play here.  I'm using a 3GHz Intel i7 with 8GB RAM.  With a database of over 5000 players, when I press the "Add Players" button on the Players tab, the dialog opens and takes about 4 seconds to display the list of names.  When I search for a player, it also takes about 4 seconds before the search is complete and the list of players updated.  15 seconds is way too long for the that initial delay, although it's *possible* the difference in hardware could account for this (but it seems unlikely to me).  50 seconds to search is clearly too long.

This is probably too much to hope for, but sometimes things like this can be explained by the way the software is being used.  For example, recently I received "Out of Memory" error reports from someone.  At different times during tournaments, the software would display this error when attempting to use various functions.  Turned out the player database had several thousand players (can't remember exactly) and for each tournament every player in the database was added to the tournament first, and then only the players that showed up were bought-in, which was usually 10 to 15 players.  So a tournament with 10 players in it actually had, say, 2000 players listed on the Players tab, 1990 of them unnecessarily.  The saved tournament files were huge, the application ran slowly, and generating statistics was painfully slow.  Removing all those extraneous players changed everything.  Any chance you're doing something along those lines?