Timeline for How to un-eat memory?
Current License: CC BY-SA 3.0
12 events
when toggle format | what | by | license | comment | |
---|---|---|---|---|---|
Jun 16, 2020 at 9:23 | history | edited | CommunityBot |
Commonmark migration
|
|
Aug 16, 2014 at 20:03 | history | edited | Ruslan | CC BY-SA 3.0 |
deleted 1 character in body
|
Dec 15, 2013 at 15:38 | vote | accept | Ruslan | ||
Dec 15, 2013 at 13:39 | comment | added | ybeltukov |
Done! P.S. RandomComplex[{0, 1 + I}, {6000, 6000}] is faster.
|
|
Dec 15, 2013 at 13:32 | answer | added | ybeltukov | timeline score: 17 | |
Dec 15, 2013 at 11:50 | answer | added | Chris Degnen | timeline score: 6 | |
Dec 15, 2013 at 10:44 | history | tweeted | twitter.com/#!/StackMma/status/412171300384571392 | ||
Dec 15, 2013 at 7:44 | comment | added | Ruslan | @ybeltukov Wow, you're right. This could make an answer. | |
Dec 14, 2013 at 22:32 | comment | added | ybeltukov |
It is just a global variable. It not clear the history. You can still access to the history by ByteCount@Out[12] or ByteCount@%10 . It can be cleared by Unprotect[In, Out]; Clear[In, Out]; but it is not a good idea.
|
|
Dec 14, 2013 at 22:23 | comment | added | Ruslan | @ybeltukov but shouldn't zeroing it clear all the history already present? | |
Dec 14, 2013 at 22:18 | comment | added | ybeltukov |
You need to put $HistoryLength = 0 before your calculations.
|
|
Dec 14, 2013 at 21:42 | history | asked | Ruslan | CC BY-SA 3.0 |