just noticed this post –
i’ve loaded tabbles on several machines and have had 0 cpu/memory contention issues.
Right now, i have Tabbles database running on a separate (home network) machine
and with >40,000 files and >200 Tabbles i’m using <10MB memory and 2-3% CPU cycles: reported in ‘Resource Monitor’ as i manipulate (add, rename, etc.) TABBLES

. . . the only thing that slows me down is the access to the full list of ‘nested’ tabbles when i “Expand All Children” – i’d guess that much of that is network latency

hope that helps

Hi there,

2.5gb of memory is definitely not ok. Whether you started an auto-tagging rule that was scanning your whole hard-drive (in that case, as the rule is over, the RAM should go back on track) or you’re hit a memory leak.

Let me know!

Andrea

I’m also having this problem.

I installed Tabbles a couple hours ago. I have 10-20 tags and around 5K files tagged. Using cloud.

Even after closing all Tabbles windows, tabbles.exe is eating 1.5GB RAM, same for its peak.

Resource Monitor reports no I/O from it. HD is pretty much not being used, only System is writing some data into Firefox profile files.

How much RAM should I expect ATM? Call me if I can help.

Hikari: it seems you’ve met a memory leak

xkat: that slow-down is much likely due to the GUI slowin down, not to database/network slowdown, as all the tabbles are already in the tree, even if they’re hidden. What videocard do you have?

i have a i5 desktop with AMD HD4850 and an i7 laptop with HD6700M – i hadn’t thought about video. I would guess that most legacy business-level machines have lower performing graphics chips, e.g Intel 3000/4000, etc.
I do 3D graphics with these machines with good performance?!?
How can i optimize for tabble display, particularly in ‘Quick-open’ pop-up?

Also, i emailed you about the loss of auto-tag function. If i “Run rules now”, TABBLES correctly tags all the files previously saved in the auto-tag directories, but it doesn’t ‘tag’ or run “show a popup” at the time the file is added, as the rule commands. This exact same (autotag) setup runs correctly on another machine.

please advise

Hi xkat,

if you have 200 tabbles and the quick-open is slow, then I guess this is a database quary that is slow. Are you using the cloud or your own SQL serve?

thanks again Andrea – local 2014 server express.
A typical SSMS query, directly on the database, takes just a few milliseconds, and tracing most stored procedures (initiated through Tabbles UI), such as getDataToComputeSuggested or computeSuggestedTabblesAndCtsofOpenTabbles take between 60-1300ms, but the display of all the tabbles in the quick-open can take over 10 seconds. Certainly this must be a display issue, but it seems it would be ‘optimizable’ somehow. no?

Also, please can you give me any hints as to why auto-tagging isn’t working (it works on my 2nd machine), but ‘run rules now’ works.