search for: 40min

Hi all! My system: R 2.1.1, Mac OS X 10.4.2. I have a very memory-consuming job for R, consisting of a function calling some other functions, working often with matrices of size 100.000 x 300. If I call the job directly after starting R the job takes overall 40min, however only 7min of process time. I assume the large difference is through memory-handling which doesn't count as process time. If i start the job after I make some shorter runs, some programming, then the job stops by reaching a memory limit. It seems that R doesn't release all t...

...ndle Firefox size programs. Honza wrote two good articles about LTO. http://hubicka.blogspot.com/2014/04/linktime-optimization-in-gcc-1-brief.html http://hubicka.blogspot.com/2014/04/linktime-optimization-in-gcc-2-firefox.html Comparison with LLVM is described in the second article. It took about 40min to finish building Firefox with llvm using lto and -g. The following is a quote: "This graph shows issues with debug info memory use. LLVM goes up to 35GB. LLVM developers are also working on debug info merging improvements (equivalent to what GCC's type merging is) and the situation has...

...en is stuck. the server is idle. Browsing to the folder shows the file to be in place. Restarting the session will cause a similar error to occur, but on some other file, after a similar amount of time. Copying the same data from a real windows machine does not have this problem, and takes about 40min in total. This is my samba configuration. Is anyone else experiencing anything similar? [global] workgroup = WORKGROUP server string = Samba Server %v netbios name = sheeran security = user map to guest = bad user dns proxy = no #allow insecure wide links = yes # performance options socket opti...

On Fri, Dec 12, 2014 at 1:59 PM, Diego Novillo <dnovillo at google.com> wrote: > On 12/12/14 15:56, Adve, Vikram Sadanand wrote: >> >> I've been asked how LTO in LLVM compares to equivalent capabilities >> in GCC. How do the two compare in terms of scalability? And >> robustness for large applications? > > > Neither GCC nor LLVM can handle our