Memory leak in server? Also - api/v1/by_location is very slow and CPU/memory intensive? about find3 HOT 5 CLOSED

I'm almost certain this has to do with my Naive bayes implementation. Can you send me your database file to checkout ? You can put in the slack channel. (Its in the /data directory with some name like *.sqlite3.db)

from find3.

Data file is attached;

bjAa.sqlite3.db.zip

from find3.

I tried with the latest git pull, after some of the recent Naive Bayes changes:

7d00ee4
591c2dc

Memory usage seems slightly better - but still very high, and doesn't release:

CONTAINER           CPU %               MEM USAGE / LIMIT    MEM %               NET I/O             BLOCK I/O           PIDS
find3server_newml   1.56%               1015MiB / 3.607GiB   27.49%              1.1MB / 448kB       63.1MB / 771MB      28

Also - the command still times out after 10 minutes:

victorhooi@victorhooi-wiki:~$ http --timeout=600 GET localhost:8003/api/v1/by_location/gcc >> ~/gcc_results

http: error: Request timed out (600.0s).

Anything else I should try?

from find3.

This should be fixed now, as I found the error was from not closing loggers when generating them.

from find3.

I notice this was closed 2 years ago but I have been experiencing something very similar. When I go into the docker container using docker exec -ti find3server /bin/bash and then running top I can see that flask memory is growing substantially (30% ) and main as well (10%). This continues to happen until restarting the container frees the memory.

from find3.