Easily find issues by searching: #<Issue ID>
Example: #1832
Easily find members by searching in: <username>, <first name> and <last name>.
Example: Search smith, will return results smith and adamsmith
| Dev |
|
| QA |
|
| Priority | Major |
| Complexity | Unknown |
| Component | Visual Analytics |
| Version | 19.0 |
I'm frequently slicing and re-slicing data within a single VA workbook and it seems to slowly increase memory usage, which is not freed even when I close the workbook. I haven't had a chance to systematically run through tests to verify this is always the case but I've heard a co-worker complain about the same so suspect there is some thing going on.
I've gotten to the point of extract the data and creating a packaged workbook just so I can quit and restart Data Studio and quickly get back to playing with the data :(
I don't think it's related to https://www.aquaclusters.com/app/home/project/public/aquadatastudio/issue/13044, at least not directly but may be due to the need to execute the query to generate the workbook?
@jasonk - we've made some memory related improvements in VA and have fixed a memory leak. Pls test out the patch below & let us know your results.
Thanks, I'll take a look and let you know what I find!
Thanks, I'll take a look and let you know what I find!
Ok-- so have run some tests, executed a large query with 700,000 rows, 40 columns.. after execution memory was at 3,679 MB, and then dropped down to 1,369 MB after some short period of time (without me doing anything-- I'm guessing it may have been memory used by the Mysql driver fetching the full result set that was then freed when it completed).
Opening the VA didn't really use any additional memory, closing the Query Analyzer did not really free any additional memory and then finally closing the VA did not free any additional memory-- leaving me at 1,369 MB. Clicking the memory trash icon several times did not do anything.
Next step will be to test without opening the VA to determine if that is related or if the memory is being held related to the Query Analyzer.
Ok-- so have run some tests, executed a large query with 700,000 rows, 40 columns.. after execution memory was at 3,679 MB, and then dropped down to 1,369 MB after some short period of time (without me doing anything-- I'm guessing it may have been memory used by the Mysql driver fetching the full result set that was then freed when it completed).
Opening the VA didn't really use any additional memory, closing the Query Analyzer did not really free any additional memory and then finally closing the VA did not free any additional memory-- leaving me at 1,369 MB. Clicking the memory trash icon several times did not do anything.
Next step will be to test without opening the VA to determine if that is related or if the memory is being held related to the Query Analyzer.
Ok, tested again. Executing the query left memory at 2,698 MB after display-- clicking the memory trash icon got it down to 1,365 MB. This time I didn't open up VA and instead just closed the Query Analyzer and then clicked the memory trash icon and it dropped memory down to 99 MB.
So it looks like there is still an issue of memory leaking from VA
Ok, tested again. Executing the query left memory at 2,698 MB after display-- clicking the memory trash icon got it down to 1,365 MB. This time I didn't open up VA and instead just closed the Query Analyzer and then clicked the memory trash icon and it dropped memory down to 99 MB.
So it looks like there is still an issue of memory leaking from VA
Ok-- another test-- this time I executed the query, opened a VA, closed the VA, closed the Query Analyzer and it was back down to 70 MB. I did this twice just to make sure :)
This is vs executing the query, opening VA, closing the Query Analyzer, and closing VA which leaves memory up.
Hence this ticket needs to be re-opened :)
Ok-- another test-- this time I executed the query, opened a VA, closed the VA, closed the Query Analyzer and it was back down to 70 MB. I did this twice just to make sure :)
This is vs executing the query, opening VA, closing the Query Analyzer, and closing VA which leaves memory up.
Hence this ticket needs to be re-opened :)
Correction on the above testing-- it was done against RedShift, not MySql.
Correction on the above testing-- it was done against RedShift, not MySql.
We have addressed several memory leaks in v18 but a few scenarios still remain. Hence, moving this to v19.
We have addressed several memory leaks in v18 but a few scenarios still remain. Hence, moving this to v19.
Verified in ADS v19.0.0-beta-30. See the reading for scenario 1 and 2 here
Verified in ADS v19.0.0-beta-30. See the reading for scenario 1 and 2 here
Issue #13369 |
| Closed |
| Fixed |
| Resolved |
Completion |
| No due date |
| Fixed Build 16.0.5-19 |
| No time estimate |
1 issue link |
relates to #13370
Issue #13370Support huge data sets in Visual Analytics |
@jasonk - we've made some memory related improvements in VA and have fixed a memory leak. Pls test out the patch below & let us know your results.