Speeding up hydrus launch

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 1 per post.

Speeding up hydrus launch Anonymous 04/23/15 (Thu) 09:20:59 No.659

Pic related it's what I'm practising.

I don't know if this interests anyone else but I've looked a little into speeding up Hydrus' launch:

1. Uninstall pyopenssl if you have it installed. This will shave just over a second off the startup time (if your computer is comparable to mine). Pyopenssl apparently decides to go and parse a bunch of C files when it's imported, which wastes time. I don't know of a better solution than just uninstalling it. https://github.com/pyca/pyopenssl/issues/137

2. If you compile everything in cython (except ClientController and ClientGUICommon, which crash in cython) it will load about 0.5s faster. I can't use very scientific timings here unfortunately, but that's what I've found. The drawback is that you'll need to edit a lot of the code before it works in cython and it will take ages to compile. Seriously that shit takes forever. Probably not worth the half second it gives.

3. Removing unused imports and moving some to a 'lazy' position. The server python files are imported from the client files, but not actually used (for the most part). Moving these out of the way did nothing noticeable to startup time at all. I was a bit optimistic here it seems.

I can't get the full launch/close cycle beneath 5 seconds by any trivial means. cProfile is a bit too rudimentary to give me any idea of what's going on, and RunSnakeRun doesn't run. If anyone has any pointers here to satisfy this one man's startup time fetish I'd be grateful.

BTW, if any Arch users here are following the AUR package, in the next couple of days I might be putting an option in the PKGBUILD for compiling in Cython. Use at your own risk, caveat emptor, etc etc. I will also be switching from using pyc to pyo by default because why the heck not.

hydrus_dev ## Board Owner 04/23/15 (Thu) 14:24:59 No.661

File: 1429799099506.jpg (123.58 KB, 824x1042, 412:521, 370bdd93f0e67bb126bc5516e1….jpg)

>>659

Thank you for these thoughts.

The client and server boot time took a dip on my dev machine this past week, so I plan to do some additional profiling to try to reduce it again. I expect, as you say, that it is mostly some bad imports.

I don't attend to this problem as much as I probably should because I keep my own personal copies of the client on my laptop open all the time.

Anonymous 04/23/15 (Thu) 19:29:52 No.662

I've updated the PKGBUILD with a cython compiler option. If you use the package, edit the pkgbuild to enable this. I might have another go at profiling too if I can figure out what tools will work for me.