search for: busier

...ringtest/run-on-all.sh b/tools/virtio/ringtest/run-on-all.sh index 52b0f71..2e69ca8 100755 --- a/tools/virtio/ringtest/run-on-all.sh +++ b/tools/virtio/ringtest/run-on-all.sh @@ -3,10 +3,10 @@ #use last CPU for host. Why not the first? #many devices tend to use cpu0 by default so #it tends to be busier -HOST_AFFINITY=$(cd /dev/cpu; ls|grep -v '[a-z]'|sort -n|tail -1) +HOST_AFFINITY=$(lscpu -p=cpu | tail -1) #run command on all cpus -for cpu in $(cd /dev/cpu; ls|grep -v '[a-z]'|sort -n); +for cpu in $(seq 0 $HOST_AFFINITY) do #Don't run guest and host on same CPU #It ac...

...ringtest/run-on-all.sh b/tools/virtio/ringtest/run-on-all.sh index 52b0f71..2e69ca8 100755 --- a/tools/virtio/ringtest/run-on-all.sh +++ b/tools/virtio/ringtest/run-on-all.sh @@ -3,10 +3,10 @@ #use last CPU for host. Why not the first? #many devices tend to use cpu0 by default so #it tends to be busier -HOST_AFFINITY=$(cd /dev/cpu; ls|grep -v '[a-z]'|sort -n|tail -1) +HOST_AFFINITY=$(lscpu -p=cpu | tail -1) #run command on all cpus -for cpu in $(cd /dev/cpu; ls|grep -v '[a-z]'|sort -n); +for cpu in $(seq 0 $HOST_AFFINITY) do #Don't run guest and host on same CPU #It ac...

...ringtest/run-on-all.sh b/tools/virtio/ringtest/run-on-all.sh index 52b0f71..0177d50 100755 --- a/tools/virtio/ringtest/run-on-all.sh +++ b/tools/virtio/ringtest/run-on-all.sh @@ -3,10 +3,10 @@ #use last CPU for host. Why not the first? #many devices tend to use cpu0 by default so #it tends to be busier -HOST_AFFINITY=$(cd /dev/cpu; ls|grep -v '[a-z]'|sort -n|tail -1) +HOST_AFFINITY=$(lscpu -p | tail -n 1 | cut -d',' -f1) #run command on all cpus -for cpu in $(cd /dev/cpu; ls|grep -v '[a-z]'|sort -n); +for cpu in $(seq 0 $HOST_AFFINITY) do #Don't run guest and hos...

...ringtest/run-on-all.sh b/tools/virtio/ringtest/run-on-all.sh index 52b0f71..0177d50 100755 --- a/tools/virtio/ringtest/run-on-all.sh +++ b/tools/virtio/ringtest/run-on-all.sh @@ -3,10 +3,10 @@ #use last CPU for host. Why not the first? #many devices tend to use cpu0 by default so #it tends to be busier -HOST_AFFINITY=$(cd /dev/cpu; ls|grep -v '[a-z]'|sort -n|tail -1) +HOST_AFFINITY=$(lscpu -p | tail -n 1 | cut -d',' -f1) #run command on all cpus -for cpu in $(cd /dev/cpu; ls|grep -v '[a-z]'|sort -n); +for cpu in $(seq 0 $HOST_AFFINITY) do #Don't run guest and hos...

...ringtest/run-on-all.sh b/tools/virtio/ringtest/run-on-all.sh index 52b0f71..38ccfa3 100755 --- a/tools/virtio/ringtest/run-on-all.sh +++ b/tools/virtio/ringtest/run-on-all.sh @@ -3,10 +3,10 @@ #use last CPU for host. Why not the first? #many devices tend to use cpu0 by default so #it tends to be busier -HOST_AFFINITY=$(cd /dev/cpu; ls|grep -v '[a-z]'|sort -n|tail -1) +HOST_AFFINITY=$(($(grep -c processor /proc/cpuinfo) - 1)) #run command on all cpus -for cpu in $(cd /dev/cpu; ls|grep -v '[a-z]'|sort -n); +for cpu in $(seq 0 $HOST_AFFINITY) do #Don't run guest and host on...

...sk create tickets in a bug tracker every time a call comes in. It's a nice way to know who's calling and why, before following up on the cause for the call. There are tons of bugtracking apps out there. Do you know of some that I should look at? Ideally, the interface shouldn't be much busier than JoS http://discuss.joelonsoftware.com/?joel . Thank you

...#39;'t get much traffic and really don''t need as much RAM as they have in them for normal day to day operations. Just let them swap everything back in and use up to the maximum RAM configured for that domain if they get busy and need it but let it swap out the rest of the time so other busier domains can use the physical RAM. This is feature #1 on my Xen wishlist. Is there any work going into this area? -- Tracy R Reed http://copilotconsulting.com 1-877-MY-COPILOT _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensou...

Having typical usage example in the README file is more convinient than in the git history... Signed-off-by: Mike Rapoport <rppt at linux.vnet.ibm.com> --- tools/virtio/ringtest/README | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/tools/virtio/ringtest/README b/tools/virtio/ringtest/README index 34e94c4..d83707a 100644 --- a/tools/virtio/ringtest/README +++

Having typical usage example in the README file is more convinient than in the git history... Signed-off-by: Mike Rapoport <rppt at linux.vnet.ibm.com> --- tools/virtio/ringtest/README | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/tools/virtio/ringtest/README b/tools/virtio/ringtest/README index 34e94c4..d83707a 100644 --- a/tools/virtio/ringtest/README +++

Hi Should we look to do a 0.0.38 release soon? I think we should get an updated set of gems out there to show we are making progress. So if you have a moment over the next couple of days, please could you post how stable a release gem from SVN HEAD is on your OS? Linux seems OK on release, crashes in debug mode - which seem to relate to the same failed assertion from wx/event.h.

Hello, rsync list folks, Recently, rsyncs abort during busier times of the day, although they run error-free during non-busy hours. Problem 1 - Many rsyncs abort these errors: Read from remote host www.xxx.yyy.zzz: Connection reset by peer rsync: writefd_unbuffered failed to write 4 bytes [sender]: Broken pipe (32) rsync: connection unexpectedly closed...

Hey - I need your input regarding a problem I''ve come across. I''ll first explain what the problem is, and what I think the solution is. If I misunderstood how things work, please let me know. # The problem I''m using Dragonfly (on-the-fly file processing) to serve images. Dragonfly uses Rack::Cache to cache the processed images so subsequent requests are served by

...r close to 100%) but nothing > does. So I managed to get current xapian.git (commit 61724d477edb) built with CXXFLAGS=-ggdb3, and it's closer to 100%: https://80x24.org/spew/20200825215517.GA3936 at dcvr/2-perf-report-20200825-214820.gz The machine I'm working on is also significantly busier at the moment trying to reproduce an unrelated problem. > > Btw, I tried google-pprof (from the Debian stable > > google-perftools 2.7-1 package) and couldn't figure it out... > > Even the example from the manpage: `google-pprof /bin/ls ls.prof` > > didn't seem to w...

On 6 Apr 2017, at 21.14, Mark Moseley <moseleymark at gmail.com> wrote: > >> >> imap-hibernate processes are similar to imap-login processes in that they >> should be able to handle thousands or even tens of thousands of connections >> per process. >> > > TL;DR: In a director/proxy setup, what's a good client_limit for >

Hi, more than a month ago I proposed an addition to the HOWTO to address a certain packet classification problem/bug and how to fix it (see http://mailman.ds9a.nl/pipermail/lartc/2005q3/016728.html). I never received any reaction from the HOWTO maintainers, not even when addressing them directly (see mail below). Given that a month has gone by: Is the HOWTO currently unmaintained? Regards,

.... This is from my experience, the much more likely and frequent problem. Where different servers, possibly unintentionally, are answering on the same network, one may often answer first for the first request, and the other may often answer first for subsequent requests, as the busier, but faster system has dhcpd swapped in. Using the two dhcp request approach may reduce problems #1 and #2. Using the single dhcp request approach reduces problem #3. Problems #1 and #2 are solid configuration errors with limited potential for trouble. If a system is using an IP address on o...

...io/ringtest/run-on-all.sh > index 52b0f71..38ccfa3 100755 > --- a/tools/virtio/ringtest/run-on-all.sh > +++ b/tools/virtio/ringtest/run-on-all.sh > @@ -3,10 +3,10 @@ > #use last CPU for host. Why not the first? > #many devices tend to use cpu0 by default so > #it tends to be busier > -HOST_AFFINITY=$(cd /dev/cpu; ls|grep -v '[a-z]'|sort -n|tail -1) > +HOST_AFFINITY=$(($(grep -c processor /proc/cpuinfo) - 1)) > > #run command on all cpus > -for cpu in $(cd /dev/cpu; ls|grep -v '[a-z]'|sort -n); > +for cpu in $(seq 0 $HOST_AFFINITY) > do...

...io/ringtest/run-on-all.sh > index 52b0f71..0177d50 100755 > --- a/tools/virtio/ringtest/run-on-all.sh > +++ b/tools/virtio/ringtest/run-on-all.sh > @@ -3,10 +3,10 @@ > #use last CPU for host. Why not the first? > #many devices tend to use cpu0 by default so > #it tends to be busier > -HOST_AFFINITY=$(cd /dev/cpu; ls|grep -v '[a-z]'|sort -n|tail -1) > +HOST_AFFINITY=$(lscpu -p | tail -n 1 | cut -d',' -f1) Shorter: lscpu -p=cpu | tail -1 Should be good enough for a test tool :) > > #run command on all cpus > -for cpu in $(cd /dev/cpu; ls|gre...

...io/ringtest/run-on-all.sh > index 52b0f71..2e69ca8 100755 > --- a/tools/virtio/ringtest/run-on-all.sh > +++ b/tools/virtio/ringtest/run-on-all.sh > @@ -3,10 +3,10 @@ > #use last CPU for host. Why not the first? > #many devices tend to use cpu0 by default so > #it tends to be busier > -HOST_AFFINITY=$(cd /dev/cpu; ls|grep -v '[a-z]'|sort -n|tail -1) > +HOST_AFFINITY=$(lscpu -p=cpu | tail -1) > > #run command on all cpus > -for cpu in $(cd /dev/cpu; ls|grep -v '[a-z]'|sort -n); > +for cpu in $(seq 0 $HOST_AFFINITY) > do > #Don't...

...> > > --- a/tools/virtio/ringtest/run-on-all.sh > > > +++ b/tools/virtio/ringtest/run-on-all.sh > > > @@ -3,10 +3,10 @@ > > > #use last CPU for host. Why not the first? > > > #many devices tend to use cpu0 by default so > > > #it tends to be busier > > > -HOST_AFFINITY=$(cd /dev/cpu; ls|grep -v '[a-z]'|sort -n|tail -1) > > > +HOST_AFFINITY=$(lscpu -p=cpu | tail -1) > > > > > > #run command on all cpus > > > -for cpu in $(cd /dev/cpu; ls|grep -v '[a-z]'|sort -n); > > > +fo...