search for: 34mb

...I replaced the binary packages libxen-4.4 and xen-utils-4.4 with the new ones. The situation is the same: the xl process for jessie amd64 guests starts off at a resident size of 15mb as opposed to ~500kb for wheezy i386 guests. At guest reboot it jumps to 17mb and then, after a few seconds, to ~34mb. I also rebooted the host to help make sure the test is valid. Thanks, Gedalya -------------- next part -------------- A non-text attachment was scrubbed... Name: 0039-do-not-leak-diskpath-during-localdisk-attach.patch Type: text/x-patch Size: 407 bytes Desc: not available URL: <http://lists....

On Thu, 2014-11-06 at 12:14 +0000, Ian Campbell wrote: > On Wed, 2014-10-29 at 17:36 -0400, Gedalya wrote: > > When booting domU's running amd64 jessie, I notice some memory problems > > with xl. > > I ran it (actually, upstream staging-4.4) under valgrind and it reported > after a reboot: > > ==5722== 24 bytes in 1 blocks are definitely lost in loss record 35

Hi Currently we are using cgroups to limit samba memory usage on our target we have limited the memory to 20MB and we are able to see samba is restricted to it. With this we are able to restrict the cache memory to ~34MB (never goes beyond this) BUt issue we arere facing is the Buffers are increasing gradually and it is not able to restrict. Commands Used to restrict memory on target: echo <samba pid >default/tasks echo 20971520 > default/memory.limit_in_bytes Initial memory status: root at ltqcpe:/sys...

Questions are threaded into the output: ******************** #./configure --without-python checking for a BSD-compatible install... /usr/bin/install -c checking whether build environment is sane... yes checking for gawk... no checking for mawk... mawk checking whether make sets $(MAKE)... yes checking build system type... i686-pc-linux-gnu checking host system type... i686-pc-linux-gnu checking

Is R file IO slow in general or am I missing something? It takes me 5 minutes to do a load(MYFILE) where MYFILE is a 27 MB Rdata file. Is there any way to speed this up? The one idea I have is having R call a C or Perl routine, reading the file in that language, converting the data in to R objects, then sending them back into R. This is more work that I want to do, however, in loading Rdata

...are. I can't figure out why it's so slow. Writes are faster than reads. My tests are a bit weird. To test out write, I write to /dev/null on the target sys, and to test read, I'm reading from /dev/zero. Locally, these copies return instantaneously. But over the network I get about 34MB/s read, and 39MB/s write. But oddly smbd is nearly 100% cpu bound. I was using 'dd' with a 1GB block size. So shouldn't 'smbd' usually have been asleep awaiting I/O completion (which is near instantaneous). I'd expect to be getting more along the lines of 60-70MB/s R+W (...

...9;t try to search substrings. Adding 255 char long non-substring searches to 4 char long substring searches grows the index about 7% (35%->42% for 32MB, 28%->36% for 200MB, 27%->33% for 1,4GB). Unfortunately it also grows memory usage pretty much. For a 200MB mailbox heap usage grows from 34MB to 163MB. For 1,4GB lkml mailbox heap usage grows from 80MB to 700MB. So I'm not sure if this should be enabled by default until something can be done about the memory usage. - The current list of indexed characters are: A-Z, 0-9, @.-+#$%_& and all 8bit chars. When trying to search for no...

...ry packages libxen-4.4 and xen-utils-4.4 with the new ones. > The situation is the same: the xl process for jessie amd64 guests starts > off at a resident size of 15mb as opposed to ~500kb for wheezy i386 > guests. At guest reboot it jumps to 17mb and then, after a few seconds, > to ~34mb. > I also rebooted the host to help make sure the test is valid. Please can you try running xl under valgrind, something similar to what I described earlier should work. Could you also post your guest cfg file please. Thanks, Ian.

...606MB from the naive in-memory logging implementation. That's a lot of data for the fully-instrumented clang version. Removing the '-fxray-instruction-threshold=1' flag defaults this to 200 instructions, and there's considerably less data logged and only from non-trivial functions (~34MB when I tested it). * The durations are in seconds, computed by taking the maximum CPU frequency. We assume that the CPU TSC counters don't drift/pause (i.e. assume "constant tic" and "nonstop tsc"). This may not be safe assumptions to make, but should be fine for the interi...

I was trying to simply test bandwidth that Solaris/ZFS (Nevada b63) can deliver from a drive, and doing this: dd if=(raw disk) of=/dev/null gives me around 80MB/s, while dd if=(file on ZFS) of=/dev/null gives me only 35MB/s!?. I am getting basically the same result whether it is single zfs drive, mirror or a stripe (I am testing with two Seagate 7200.10 320G drives hanging off the same interface