Hydrus Speed

Name
Email
Subject
Comment *
File	Select/drop/paste files here
* = required field	[▶ Show post options & limits] Confused? See the FAQ.

Embed	(replaces files and can be used instead)
Options	Do not bump (you can also write sage in the email field) Spoiler images (this replaces the thumbnails of your images with question marks)
Password	(For file and post deletion.)
Allowed file types:jpg, jpeg, gif, png, webm, mp4, swf, pdf Max filesize is 8 MB. Max image dimensions are 10000 x 10000. You may upload 5 per post.

File: 1429121757962.png (932.91 KB, 800x838, 400:419, Lilith - こいし (19747822) .png)

Hydrus Speed Anonymous 04/15/15 (Wed) 18:15:58 No.639

Hello again. I've been using Hydrus for a few days. Well, rather I've used it before and I'm getting back into it. I wanted to organize all the things I've been pulling from pixiv and tag them based on danbooru tags. That way I could export and appropriately dump art.

My main problem right now is the speed, it was the same problem when I first tried using hydrus months back. At first, it's really fast and could grab my 3000 images for me with no problem, but after I started adding more tags, it got much harder. I used the danbooru tag archive you had on mediafire and now it's just outrageously slow.

Right now, I'm having it search for all the files I have under series:touhou. I started the search at 14:01 EST. It's currently 14:14 as of this sentence and it has made it to "768 of 1566". So, I'm looking at 256 images every ~4 minutes. I don't know if this is a normal thing, if I failed to set something up, or if my 8 year old prebuilt Gateway desktop that I'm running this on is just not cut out for mass image tagging. But I'd appreciate any kind of information of reasons as to why this isn't working out.

Anonymous 04/15/15 (Wed) 21:15:24 No.640

>8 year old prebuilt Gateway desktop
I think you just answered your own question. Maybe defrag the HDD, but the HDD is likely slow as sin so that probably won't do much.

Anonymous 04/15/15 (Wed) 22:02:53 No.641

File: 1429135373614.jpg (461.33 KB, 1000x1000, 1:1, 小桜まさ - ○l￣l＿ (27284707) 1ペ….jpg)

>>640
If you're saying something like that, I can only assume this is just an issue with my machine itself. I'll try a defrag but I don't expect much out of that. All the more reason to get a job, get money, and build something myself, I guess.
Thanks.

Anonymous 04/16/15 (Thu) 06:43:47 No.642

File: 1429166627604.jpg (75.12 KB, 510x560, 51:56, 431d25f27d24deba86fdf9bc63….jpg)

And it also seems like you're pretty much right. Testing on another machine (Linux laptop) is running fast as I expected it to be. It has its own share of problems. Some tags, notably non-wildcarded tags with a high image count, give me:
>The program 'client.pyw' received an X Window System error.
>The error was 'BadAlloc (insufficient resources for operation)'
But it is most definitely running a lot smoother. I'll have to adjust my usage of this around my laptop now.

hydrus_dev ## Board Owner 04/19/15 (Sun) 22:19:09 No.648

File: 1429481949519.jpg (172.67 KB, 1235x1023, 1235:1023, 6d641f28d8451efd02f7ee3afb….jpg)

Hey, sorry for the late reply here.

Usually the client down slows down because:

Your drive is close to being full and/or very fragged

Your drive is really old, slow, or encrypted and running through an old CPU

Your drive is being used by another HDD-heavy process (like another active hydrus client or a defragger, lol)

You have loads of files in your inbox

I wrote some other bad code that is running specifically slow on your machine.

I fixed the large-inbox-slows-result-construction bug this week, so if that is true, please try again with v154. Also, I have added a comprehensive db-profiling mode in v154, which will record how long any kind of database access takes and dump lots of related information into the log. It would be very useful for me if you ran some profiles on your slow computer next week and sent me those results, as I can figure out exactly what is taking so long and clean it up. I will explain more about this new profiler in my v154 release post.

On your laptop, do those memory allocation errors cause the program to crash completely, or do you get a popup inside the client?

Anonymous 04/21/15 (Tue) 02:55:17 No.652

File: 1429584917888.jpg (288.98 KB, 1144x1672, 13:19, らぱ☆例大祭N08a - こいしちゃんと青い紐 (4….jpg)

>>648

Thanks. My drive was pretty full at the time. So I'll try it again.

The memory stuff crashes the entire thing at once.

There were also some critical warnings that flared up as well. I don't know if it's related to why it crashed but it seemed like it was crying about the GUI.

OP 01/06/16 (Wed) 13:53:32 No.1711

File: 1452088413006.png (807.35 KB, 1024x1452, 256:363, a46374e2f197775e28ca3fb486….png)

Hey. I haven't been following the updates much and I gave up after a while those couple of months ago. However, I just grabbed version 187 about a week or so ago and I no longer have this problem. Keep up the good work.