On Thu, 19 Sep 2019, J wrote:
> In detail I found the syndrome_decoders crashes while initiating with
> big codes as the system runs out of memory
Hmm... An idea:
$ fgrep VmPeak /proc/6649/status
VmPeak:31204 kB
(6649 is PID of my bash)
If you add delay to the end of sage script, you could
More or less this yes;
But it seem I will stick to putting it in a sage ipyhton session wrapped
in a screen session
In detail I found the syndrome_decoders crashes while initiating with
big codes as the system runs out of memory
and that prompted me to plot RAM vs max_error for the syndrome deco
On Wed, 18 Sep 2019, J wrote:
> The most problematic part for me is:
>
> I would like to script it
I'm not sure what you mean. You have some list L of objects, and want to
know how much memory it takes to run f(x) for each x in L?
--
Jori Mäntysalo
Tampereen yliopisto - Ihminen ratkaisee
--
The most problematic part for me is:
I would like to script it
On 19-09-18 10:20:12, Jori Mäntysalo (TAU) wrote:
> On Tue, 17 Sep 2019, J wrote:
>
> > TBH I can't get it to work
> > and
> > "sagemath %mprun"
> > gives to pages of search results including this thread ^^
>
> Duh. Somebody should ad
On Tue, 17 Sep 2019, J wrote:
> TBH I can't get it to work
> and
> "sagemath %mprun"
> gives to pages of search results including this thread ^^
Duh. Somebody should add a page on this to the doc.
First, said
./sage -pip install memory_profiler
and then normally
./sage --notebook=jupyter
In
On 19-09-03 09:43:23, Jori Mäntysalo (TAU) wrote:
> On Mon, 2 Sep 2019, J wrote:
>
> > Thanks get_memory_usage sounds good; I want to run several decoders from
> > the coding theory module to see better show there ups and downs;
>
> There is also at least %mprun magic. Googling that will give you s
On 19-09-03 11:31:32, Nils Bruin wrote:
>
>
> On Tuesday, September 3, 2019 at 2:43:27 AM UTC-7, Jori Mäntysalo (TAU)
> wrote:
> >
> > There is also at least %mprun magic. Googling that will give you some
> > examples.
> >
> > Looking at the memory footprint of the entire process (as a function of
On Tuesday, September 3, 2019 at 2:43:27 AM UTC-7, Jori Mäntysalo (TAU)
wrote:
>
> There is also at least %mprun magic. Googling that will give you some
> examples.
>
> Looking at the memory footprint of the entire process (as a function of
time) gives some indication of memory use of a certa
On 2019-09-03, Jori Mäntysalo wrote:
> On Mon, 2 Sep 2019, J wrote:
>
>> Thanks get_memory_usage sounds good; I want to run several decoders from
>> the coding theory module to see better show there ups and downs;
>
> There is also at least %mprun magic. Googling that will give you some
> example
On 19-09-03 09:43:23, Jori Mäntysalo (TAU) wrote:
> On Mon, 2 Sep 2019, J wrote:
>
> > Thanks get_memory_usage sounds good; I want to run several decoders from
> > the coding theory module to see better show there ups and downs;
>
> There is also at least %mprun magic. Googling that will give you s
On Mon, 2 Sep 2019, J wrote:
> Thanks get_memory_usage sounds good; I want to run several decoders from
> the coding theory module to see better show there ups and downs;
There is also at least %mprun magic. Googling that will give you some
examples.
--
Jori Mäntysalo
Tampereen yliopisto - Ih
On 19-09-02 10:35:18, Simon King wrote:
> Hi J,
>
> On 2019-08-24, J wrote:
> > to do a overview of a rather different set of `SAGE` methods, I would
> > like to not only track the time used to run a command, but also the
> > memory usage of the commands.
> >
> > Is there a recommended way to do t
Hi J,
On 2019-08-24, J wrote:
> to do a overview of a rather different set of `SAGE` methods, I would
> like to not only track the time used to run a command, but also the
> memory usage of the commands.
>
> Is there a recommended way to do this?
I am a bit surprised that nobody answered this qu
13 matches
Mail list logo
