Large library scanning issue.
Issue #2
open
Wayne S: I'm not having much luck getting comics to show on my desktop either. Could this be the size of my library( Its about 60,000 comics)? I've tried using both quick and cover scan. With the latter, I see the red rotating dots in the top left for about 5 seconds and then it stops.
Comments (7)
-
reporter
-
reporter
- changed status to open
Potential fix in next release.
-
Let me know if theres anything I can do to help, appreciate you even looking in to this.
For what its worth, my desktop which is running a wired gigabit connection and has plenty of RAM (16gb, which is probably more than most). In terms of Wifi testing, I have 802.11ac (although my tablet only supports N) so I can test a couple of scenarios if and when you're able to resolve.
Actually, thinking about it, I guess I can rule out network because my desktop is also my comic server!
-
reporter
Just having users and getting good feedback is great! I really want the app to be good so fixing problems isn't an issue! There is a new version out on the store, if you could update and try that it'd be great. Although I'm getting a little worried about caching thumbnails now, especially for such a large library, working it out from 60,000 comics and thumbnails at 80KB the cache for your library would be ~4.5GB! I've got a solution in mind for this but there's some ground work needed first.
-
Not a problem at all, I know nothing about coding (I work in IT but on the support side) so I'm grateful theres people like you out there, I'm just happy to help where I can!
On the thumbnail front, I would take the view that if someone has the room for 60,000+ comics, they probably have the room for 4.5gb of thumbnails :) Maybe put a note on the app store to make people aware of it, but so long as your app can handle a directory that big, I don't think you need worry - especially if at some point you offer the ability to set the cache location.
I suppose actually for tablet users it could be an issue, so again the cache location (moving to an SDCard for example) will greatly help.
That said, I don't know if this helps you, but my actual Ubooquity cache is 600mb, thumbnails are 150x230 and weighing about 8k each. Obviously Tom has some resizing of the image going on, but I wouldnt say (personally) implementing that is a priority for your app at this point.
Just trying the app now on my desktop - looks like its still indexing which is a good sign. Will update this post when it finishes.
Edit: Pasting from the 32bit App thread:
On the tablet I can see my comic folder structure and navigate through it. Couple of issues however (I'll cross post these in to the library size thread):
-
Number of comic in a folder always shows as 0 - this might be because its not completing the initial scan? I'm able to start navigating immediately so I'm guessing its maybe timing out once its pulled the folder structure?
-
The app closes (no error message) when I either go in to a folder with lots of entries - one folder I tested had 62 comics in it - app just closed when I assume it was generating thumbnails?
-
Testing with a smaller folder (3 comics), I get the thumbnails but upon opening a comic, the app closes again as above - I'm dumped back to the desktop.
On my desktop, using the 64bit version, I'm still not able to see any folder structure. I've removed the app and reinstalled to see if that fixes the problem and make sure I'm on the latest version, but it didnt help.
Can you explain what the different colours on the rotating circle mean? I get a cyan version for about 5 seconds after adding the server or hitting the refresh button, but then it stops. I've also seen white and I think, I once saw red. Are these different read states?
Hope that helps!
-
-
reporter
There's a lot here and covers quite the range so I'll work backwards since it seems easier.
The coloured circles do have meaning,
-
Red: Scanning Directories.
-
Green: Scanning Issues.
-
Cyan: Fetching thumbnails.
-
Grey: Database interaction.
They're mostly there for me at the moment but it looks like they're more useful than I thought.
It's really weird that you're having so much trouble with the 64bit version. It could be related to the desktop being your server. Are you using "127.0.0.1" as your local ip, your lan ip (probably 192.168.0.XXX) or a URL for connecting?
The random crashes: are you installing Variant onto a HDD? While I tried to prevent too many simultaneous connections to the server I didn't do the same for reading/writing from/to a HDD and this can cause errors which I've handled poorly. While testing an install on the HDD I also noticed that image quality was inferior when installed on a HDD vs an SSD which is odd so I'll look into that too.
It seems like the Directory/Issue scan has completed try hitting the refresh button on pages where it still says 0, that should cause them to recalculate the numbers. I put a 15 minute time interval in between updates to the numbers so that it wouldn't update every time you opened up a directory.
As for the cache, you're right it probably isn't a problem and a warning should suffice.
Cheers for all the feedback, I'll see how much I can get sorted this weekend although any updates are at least a week away.
-
-
Yeah the colours are definitely useful and worth keeping in imo.
Nope, I'm connecting to the IP address (http://192.168.x.x)
On my desktop, I have Ubooquity installed on to an SSD, although you're right on the tablet, its installed on to an SD card, so I'll look to switch that - I might run in to problems with the cache at that point though, so for tablet testing I'll probably have to wait for the option to move the cache.
- Log in to comment
Right this is quite a problem. I suspect the most likely reason is due to a mistake I made while implementing the database code where every entry is added one at a time. Since then I've learned about sqlite "transactions" and I'm not doing large batches of database inserts as a single transaction. This is included in the next version. Whether this will fix the issue is difficult for me to say, it's possibly also a network connection issue, in which case I have to do some redesigning of the code.