/hydrus/ - Hydrus Network

>and some important stability improvements, particularly for Linux.

YAYYYYYYYYYYYYYYYYYYYYY

>>11716

>more memory reduction

How is this even possible? At this rate we'll be at near-zero memory usage by v. 500

>>11716

Nice

>and some important stability improvements, particularly for Linux.

So my client's been crashing (like segfaulting, not an unrecoverable python error) pretty much constantly since I upgraded from 338 to 340, perchance should these fix that?

If not then fuck me for overwriting my backup with a 340 backup.

https://kanban-1.herokuapp.com/boards/9

>>11721

Trying to find a kanban for people to put their ideas on the board.

>>11718

the program tends to eat memory when you heavily use it, let me give you a picture of what I mean

I save every thread on 4chan that catches my interest, at some point the reposts start to overtake the new images to a point that this is a viable option, thy im getting close to the edge of I need some delete functionality for telling me what the file was deleted for. that aside, right now, over the coarse of 2 months I have created around 6400 watchers, adding somewhere around 150-200k images, almost none of them are displayed, with around 100k displayed.

the 100k displayed images takes about 1.5-2gb, I know this from the time I culled the watchers, my current session is 4.3gb and bloats out to 6.5gb on saves.

I have absolutely no idea what takes ram, if they were all current watchers, ok, I would believe that, but from experience current watchers for all the threads adds up to around 500mb or less, so for some reason, the program is using an ungodly amount of ram for reasons that are unclear because just storing all of the the data in text form could not possibly add up to over 20mb much less what I estimate at being over 2gb with a doubling in save.

I should also note that I come from a session that was hitting 14gb on startup and when a save happened would bloat to 18+gb

depending on where hdev is focusing, memory reduction has many different ways to happen.

>>11724

>the program tends to eat memory when you heavily use it

I think that goes for most programs.

When I had 8GB of RAM my average overall usage was around 3GB, but now that I have 16GB it averages 6 or 7 even though I'm doing the same things.

>>11718

Bare client is about 115MB ram on Windows, so the absolute minimum is pretty low compared to what many users see. I am about 490MB on my IRL laptop that has about 17k items in its main session (mostly thread watchers).

The python 3 change lead to some pseudo-memory-leaks, so that was a recent chunk I was able to recover, and I am making an important db-memory change in 341 today.

I would appreciate continued feedback here. There isn't a huge amount I can do atm about clients that have hundreds of thousands of pending URLs in their session, but PTR update processing and some other db stuff should be much less traumatic now. There's still more to do, and I still plan to make a memory profiler this year to draw some pie charts or something and squeeze this further.