Ok, I found the solution Mr Bag! So, the reason Fat16 goes so fast for you is probably because the default Allocation Unit Size is 64KB, if you are using 4GB, which I am guessing you do use that.
So, I went and formatted my 8GB card as FAT32, my only real option, and then chose 64KB as the Allocation Unit Size, instead of the default 32KB. And suddenly, things were lightning fast.
One HUGE downside to this is every single one of those covers I have now is 64KB. Since I haven't selected specifically covers to only games I own, there is about 3500 files, give or take. This means while the size of the files is only 61MB or so, the actual space it requires is 220MB. Youch. But much more insanely faster browsing speed. I wonder why your program specifically love 64KB? 32KB runs blazing fast in the standard UI. BTW if you use a FAT16 card smaller than 4GB, you won't have 64KB allocation, and as far as I know, you can't change that. 2GB = 32KB, 1 GB= 16KB and so on...
I wonder if you used a 2GB card, or smaller, even in FAT16, if it would be really slow? In that case you still can convert it up to FAT32 with 64KB allocation.
So, even though I can't test it as thoroughly as I want, I can without a doubt say that FAT16 vs FAT32, doesn't matter. It is the Allocation Unit Size you choose.
EDIT: Wanted to point out that I have about 115 DS games, with 349 total files in the root directory. With CPU setting on 120 and pushing right to fastscroll to the bottom, it takes 6.4 seconds. CPU set to 240, it takes 4.4 seconds. Full blast at 396 takes 3.4 seconds. Thats freaking amazing. Also when you press start it doesn't take 5 seconds to open anymore, its instant. The whole thing was blooming slow even when there weren't any files on the card except the UI itself. So, something in your program absolutely loves 64KB Allocation. And doesn't like 32KB thats for sure. Now the only thing left is to add a way to change cheats!
2nd EDIT: Yah, I'm pretty sure the top_display_refresh variable is a big waste of time too. If you are scrolling as fast as you can, you are holding the button down, and it doesn't load pictures when you do that. So, making it take a second to load box art doesn't affect scroll speed unless you tend to scroll slowly anyways and let go of the button each time. I also just timed the "slow" scroll, holding down going through each one. With CPU set to 396, it takes 7.4 seconds. Good lord it moves fast. I really think you oughta change the first post to mention how amazing life gets if you reformat to 64KB Allocation. Haha, I went from 250 to 28MB free out of 7.59 GB. Worth it for the speed boost though.
So, I went and formatted my 8GB card as FAT32, my only real option, and then chose 64KB as the Allocation Unit Size, instead of the default 32KB. And suddenly, things were lightning fast.
One HUGE downside to this is every single one of those covers I have now is 64KB. Since I haven't selected specifically covers to only games I own, there is about 3500 files, give or take. This means while the size of the files is only 61MB or so, the actual space it requires is 220MB. Youch. But much more insanely faster browsing speed. I wonder why your program specifically love 64KB? 32KB runs blazing fast in the standard UI. BTW if you use a FAT16 card smaller than 4GB, you won't have 64KB allocation, and as far as I know, you can't change that. 2GB = 32KB, 1 GB= 16KB and so on...
I wonder if you used a 2GB card, or smaller, even in FAT16, if it would be really slow? In that case you still can convert it up to FAT32 with 64KB allocation.
So, even though I can't test it as thoroughly as I want, I can without a doubt say that FAT16 vs FAT32, doesn't matter. It is the Allocation Unit Size you choose.
EDIT: Wanted to point out that I have about 115 DS games, with 349 total files in the root directory. With CPU setting on 120 and pushing right to fastscroll to the bottom, it takes 6.4 seconds. CPU set to 240, it takes 4.4 seconds. Full blast at 396 takes 3.4 seconds. Thats freaking amazing. Also when you press start it doesn't take 5 seconds to open anymore, its instant. The whole thing was blooming slow even when there weren't any files on the card except the UI itself. So, something in your program absolutely loves 64KB Allocation. And doesn't like 32KB thats for sure. Now the only thing left is to add a way to change cheats!
2nd EDIT: Yah, I'm pretty sure the top_display_refresh variable is a big waste of time too. If you are scrolling as fast as you can, you are holding the button down, and it doesn't load pictures when you do that. So, making it take a second to load box art doesn't affect scroll speed unless you tend to scroll slowly anyways and let go of the button each time. I also just timed the "slow" scroll, holding down going through each one. With CPU set to 396, it takes 7.4 seconds. Good lord it moves fast. I really think you oughta change the first post to mention how amazing life gets if you reformat to 64KB Allocation. Haha, I went from 250 to 28MB free out of 7.59 GB. Worth it for the speed boost though.
BassAceGold said:lex luthor said:@OP
I own a 16gb micro sd so what do you recommend I should do to scroll roms faster?, because they scroll a little slow.
QUOTE(BassAceGold @ Mar 26 2011, 02:04 PM) Improving BAGplug Performance
BAGplug does quite a bit of random reading from the SD card for things such as icons and box art. These can cause lagging or bad performance when scrolling through files. Here are a few tips to optimize BAGplug to (hopefully) make it run smoother:
-Make sure your SD card is formated to FAT or FAT16 (for 4GB cards or smaller)
-Box art is loaded after X (5 is the default) number of program cycles without user input in the browser. You can change this value in your settings.ini with the 'top_display_refresh' variable. 60 = 1 second, 30 = half a second etc. The default value may be to fast and cause lagging when scrolling with covers.
-Last resort: Change the CPU speed in the BAGplug options menu. A reboot of the menu may be needed to get working properly after switching CPU speeds.
Another thing you could try is disabling the use of internal rom names. Other than that there is nothing much else that can be done. The icons can only be read so fast from the SD card. If things are getting really slow, maybe try breaking large directories of roms into smaller bunches ~50 files or less. I notice that file system reads are much much slower than average when reading from a directory with hundreds of files.












