Hello The Bat Users!
I am one of the many users having this "database indexing" problems.
Here is some info I have noticed when using The Bat v11
- Database indexing runs after each restart, with me that is next day in the morning.
- Even after indexing completes, the Search function is SLOOOOW on my desktop.
- The Search funtion on my 9 year old laptop is MUCH faster, even though my desktop is a much more powerfull system.
- Yes, I do have my user and email folders on a hdd instead of SSD, but the search on the HDD used to be fast also.
Especially this current HDD is a Western Digital Enterprise Gold disk Series....it's fast as f@ck!
- Disabling the threaded view and using the Classic view does not make ANY difference.
- You do not need any special tools to see hard disk usage by process or exe file, just run Resource Monitor in windows 10 or 11.
In my case I see hundreds and hundreds of instances of thebat.exe doing the database indexing each several dozen KB, but all together quite a few MB's per second!!......trashing the HDD.
- This obviously hasn't been thought trough very well.....SqlLight is as crap as you can get and should NEVER ever been used for this. Obviously a full fledged SQL server is also not the way to go for a consumer desktop application. There are MANY other ways this could have been solved that are way better.
- For now I have disabled the indexing function......but it still boggles the mind why a decade old laptop is much faster when using the search option??
I really hope Ritlabs will solve this in an efficient manner instead of a "quick patch", I am willing to wait on a good solution.
I am one of the many users having this "database indexing" problems.
Here is some info I have noticed when using The Bat v11
- Database indexing runs after each restart, with me that is next day in the morning.
- Even after indexing completes, the Search function is SLOOOOW on my desktop.
- The Search funtion on my 9 year old laptop is MUCH faster, even though my desktop is a much more powerfull system.
- Yes, I do have my user and email folders on a hdd instead of SSD, but the search on the HDD used to be fast also.
Especially this current HDD is a Western Digital Enterprise Gold disk Series....it's fast as f@ck!
- Disabling the threaded view and using the Classic view does not make ANY difference.
- You do not need any special tools to see hard disk usage by process or exe file, just run Resource Monitor in windows 10 or 11.
In my case I see hundreds and hundreds of instances of thebat.exe doing the database indexing each several dozen KB, but all together quite a few MB's per second!!......trashing the HDD.
- This obviously hasn't been thought trough very well.....SqlLight is as crap as you can get and should NEVER ever been used for this. Obviously a full fledged SQL server is also not the way to go for a consumer desktop application. There are MANY other ways this could have been solved that are way better.
- For now I have disabled the indexing function......but it still boggles the mind why a decade old laptop is much faster when using the search option??
I really hope Ritlabs will solve this in an efficient manner instead of a "quick patch", I am willing to wait on a good solution.