similar to: reclaiming lost memory in R

I have data that looks like this: > df1 group id 1 red A 2 red B 3 red C 4 blue D 5 blue E 6 blue F I want a list of the groups containing vectors with the ids. I am avoiding subset(), as it is only recommended for interactive use. Here's what I have so far: df1 <- data.frame(group=c("red", "red", "red", "blue",

Hello, I have a general question on the possibility of how to "catch and stop" a function when it uses too much memory. The problem is that some datasets, when applied to nlme (a relatively older version), cause the nlme function to just hang forever and start taking over memory (this afternoon one of those calls was about 40GB!) and not returning an answer. Other datasets work fine.

Check the page refcount rather than the type count when deciding if a page is still mapped. This catches pages which are mapped by qemu; it also removes the need for gnttab_is_granted(). Signed-off-by: George Dunlap <george.dunlap@eu.citrix.com> _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel

Hello, Is there a command for freeing up the memory used by R in holding data tables? The structure of the procedure I have is as follows: 1) Read multiple txt files in using read.table(...). 2) Combine the read tables using rbind(...). 3) Attach the data using attach(...) and then use do a multiple regression using lm(...). So far so good, but when I then perform a further regression by

When trying to do a yum update, I am told I need more space in /boot. When I check the contents of /boot (ls -l /boot), there are no files. If I do a df -h, there is no available space yet it shows that it has a lot of used space. The fstab shows the following: # This file is edited by fstab-sync - see 'man fstab-sync' for details /dev/VolGroup00/LogVol00 /

The following is mainly a capture of parts of multiple off-line discussions within members of the Crossbow team (Gopi, Thiru, Roamer, May-Lin, Thirumailai, Nitin, KB, ...), I thought I''d open it up to other participants. Crossbow''s core scheduling involves switching a NIC (or individual Rx rings on the NIC) to polling mode. The receive interrupt will become not only rarer,

On 1/3/19 6:37 AM, Richard W.M. Jones wrote: > The original plan was to have a background thread doing the reclaim. > However that cannot work given the design of filters, because a > background thread cannot access the next_ops struct which is only > available during requests. > > Therefore we spread the work over the request threads. Each blk_* > function checks whether

On 1/1/19 8:33 AM, Richard W.M. Jones wrote: > The original plan was to have a background thread doing the reclaim. > However that cannot work given the design of filters, because a > background thread cannot access the next_ops struct which is only > available during requests. > > Therefore we spread the work over the request threads. Each blk_* > function checks whether

The original plan was to have a background thread doing the reclaim. However that cannot work given the design of filters, because a background thread cannot access the next_ops struct which is only available during requests. Therefore we spread the work over the request threads. Each blk_* function checks whether there is work to do, and if there is will reclaim up to two blocks from the cache

The original plan was to have a background thread doing the reclaim. However that cannot work given the design of filters, because a background thread cannot access the next_ops struct which is only available during requests. Therefore we spread the work over the request threads. Each blk_* function checks whether there is work to do, and if there is will reclaim up to two blocks from the cache

The original plan was to have a background thread doing the reclaim. However that cannot work given the design of filters, because a background thread cannot access the next_ops struct which is only available during requests. Therefore we spread the work over the request threads. Each blk_* function checks whether there is work to do, and if there is will reclaim up to two blocks from the cache

The original plan was to have a background thread doing the reclaim. However that cannot work given the design of filters, because a background thread cannot access the next_ops struct which is only available during requests. Therefore we spread the work over the request threads. Each blk_* function checks whether there is work to do, and if there is will reclaim up to two blocks from the cache

Patch 1 is the same as last time, except for a minor comment fix. Patch 2 should address everything that Eric mentioned in his review, and has been retested. Rich.

For help: for loop lead to stack overflow, want to actively reclaim stack memory of alloc instruction. How to actively reclaim stack memory ? haifeng.qin at wellintech.com -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20161215/54b3b18c/attachment.html>

On 15 Dec 2016, at 07:26, haifeng.qin at wellintech.com via llvm-dev <llvm-dev at lists.llvm.org> wrote: > > For help: > > for loop lead to stack overflow, want to actively reclaim stack memory of alloc instruction. > > How to actively reclaim stack memory ? This sounds as if you’re putting the alloca inside the loop, not in the entry basic block and reusing it. If you

Frank Thommen wrote: > > Hi, > > since I updated my workstation from CentOS 7.4 to 7.5, Firefox and > Thunderbird (both 52.8.0, from CentOS repos) regularly freeze (or crash) > and cannot be restarted afterwards.? Trying to start them results in a > "Bus error (core dumped)" (Firefox) and "Killed" (Thunderbird).? The > system log then shows: > >

I was afraid someone would say that :-). I am currently at 3.10.0-862.3.2 and downgrading to a 3.10.0-6xx kernel breaks some of the other packages. Is the mentioned bug documented somewhere? Cheers frank On 07/06/18 06:22, James Peltier wrote: > There was a kernel bug that affected all NFSv4 traffic that we ran into > and we had to downgrade the kernel to and older version >

For FreeBSD 4.7 I've discovered the cause of the deadlock, but I can't figure out how to fix it. See below for traces. If the vnode limit has been reached, the vnlru process is kicked and the requestor goes to sleep to wait for the vnlru process to signal that vnodes are available (10% of the vnodes need to be freed). Under our test, none of the nodes meet the criteria for freeing,

Hello, happy new year. When many Windows clients access the shares but don't perform any operations, will the child processes forked by smbd be reclaimed? If they are reclaimed, what factors influence this time? Best wish. Jam

Dear all, I am puzzled by R's memory usage when calling the blackboost function from package mboost to estimate a Gradient boosting model on a simulated dataset with 20 correlated variables and 100,000 obs. The blackboost object created by the function is only 15.3Mb, but R's memory usage increases by about 3.9Gb during the estimation of the model and the memory is not released even after