High memory usage

[lavalamp]

hey there martin. Im using the latest version 3.4.7.864 and I noticed a high memory usage. It is using 80-90% of my memory most of the time
and Im not using the "in memory processed logs"

I think this was something to do with "watchfornewfollower" action taking additional threads. (just a hunch) because watchfornewfollower action is running/processing even when in waiting status.

or in memory processed logs are in effect even if its turned off

May you kindly check it






on the previous version that i was used It only consume less 20% of ram
ram is 5GB
processor is 2.60GHz

[martin@rootjazz]

I think this was something to do with "watchfornewfollower" action taking additional threads

I don't see how that could be responsible. The action will run on a timer.

check for new followers via followers scrape
wait (x) seconds
repeat

goto
%appdata%\rootjazz\twitterdub\database\DbLoggedData


order by size, what are the largest file sizes?

How many accounts do you have?
How many actions in the processor?

Restart the app (with auto run turned off)
What memory is being used?

[lavalamp]

Is there any other report about this version 3.4.7.864? or its just me?

I have tested and can confirm that watchfornewfollower action is using additional threads. I mean i set the threads to 1 but I can see that it was using more than 1 threads (checking 2 accounts at the same time, DM'ing more than 1 at the same time. etc.). it was processing even when paused or in waiting status.

theres also an incident when I run the app (with just 1 thread) all of the action in waiting status run altogether

about your question. largest file is only 186KB
1222 accounts
actions in processor is 75
App restarted and its using 1%CPU and 53% memory


If i reinstall the app? will the file/accounts will be gone/deleted or it will stay there even when i reinstall it?

[martin@rootjazz]

Is there any other report about this version 3.4.7.864? or its just me?

Just you

I have tested and can confirm that watchfornewfollower action is using additional threads. I mean i set the threads to 1 but I can see that it was using more than 1 threads (checking 2 accounts at the same time, DM'ing more than 1 at the same time. etc.). it was processing even when paused or in waiting status.

Submit logs please

theres also an incident when I run the app (with just 1 thread) all of the action in waiting status run altogether

Start app, with auto run off
Clear logs: HELP > LOGS > DELETE
Change threads to 10, wait 5 seconds
Change threads to 1 wait 5 seconds
Click RUN
wait 5 seconds, submit logs:
HELP > LOGS > SUBMIT

then send your logs ID - the numbers are sufficient (displayed after successful uploading of logs)

viewtopic.php?f=32&t=12078

about your question. largest file is only 186KB
1222 accounts
actions in processor is 75

goto
%appdata%\rootjazz\twitterdub\database\
right click \dbaccount\ and select properties. What is size of folder?

Same for \dbaction\

Same for \dbloggeddata\

App restarted and its using 1%CPU and 53% memory

53% and your machine is 5gb I think you said, OS is using 1gb, so TD using 2gb, it's high, but you have 1000 accounts, it's not excessive. You may just need to increase RAM for 1000+ accounts that have been used a while and started to store more data

If i reinstall the app? will the file/accounts will be gone/deleted or it will stay there even when i reinstall it?

the data will NOT be deleted. The only way the data is removed, is if you do it manually. I doubt reinstalling will do anything tbh

[lavalamp]

hey there. how about this. i will just delete TD and install it again so its just like installing TD in a new machine ( i have save the files i needed )

what files and folder do i need to delete

[lavalamp]

nevermind this.


already solved it

[martin@rootjazz]

hey there. how about this. i will just delete TD and install it again so its just like installing TD in a new machine ( i have save the files i needed )

what files and folder do i need to delete

you can do this with a custom database instance.
For some info on custom db instances, check the thread

viewtopic.php?f=15&t=9348


This will open twitterdub with a new database folder so it's like a clean install (no actions / no accounts). You can open up as many instances as your machine will allow (about 20 usually).

You can add the same accounts if wanted to test something, or just to spilt accounts on different instances.


If you want to move to a difference machine your database folder is:
%appdata%\rootjazz\twitterdub\database\

just copy that over.