search for: 338ms

...s bad for > > performance improvement. Right? > > It's a tradeoff for sure. Measure it, see what the overhead is. > Hi MST, I have measured the performance when using a 32K page bitmap, and inflate the balloon to 3GB of an idle guest with 4GB RAM. Now: total inflating time: 338ms the count of virtio data transmission: 373 the call count of madvise: 865 before: total inflating time: 175ms the count of virtio data transmission: 1 the call count of madvise: 42 Maybe the result will be worse if the guest is not idle, or the guest has more RAM. Do you want more data? Is it w...

...s bad for > > performance improvement. Right? > > It's a tradeoff for sure. Measure it, see what the overhead is. > Hi MST, I have measured the performance when using a 32K page bitmap, and inflate the balloon to 3GB of an idle guest with 4GB RAM. Now: total inflating time: 338ms the count of virtio data transmission: 373 the call count of madvise: 865 before: total inflating time: 175ms the count of virtio data transmission: 1 the call count of madvise: 42 Maybe the result will be worse if the guest is not idle, or the guest has more RAM. Do you want more data? Is it w...

...9;t assign the PFN when allocating page in balloon driver, So the PFNs of pages allocated may be across a large range, we will tell the host once the pfn_max -pfn_min >= 0x40000(1GB range), so the requests count is most likely to be more than 3. > > Now: > > total inflating time: 338ms > > the count of virtio data transmission: 373 > > Why was this so high? I would expect 3 transmissions. I follow your suggestion: ------------------------------------------------------------------------------------ Suggestion to address all above comments: 1. allocate a bunch of pa...

...9;t assign the PFN when allocating page in balloon driver, So the PFNs of pages allocated may be across a large range, we will tell the host once the pfn_max -pfn_min >= 0x40000(1GB range), so the requests count is most likely to be more than 3. > > Now: > > total inflating time: 338ms > > the count of virtio data transmission: 373 > > Why was this so high? I would expect 3 transmissions. I follow your suggestion: ------------------------------------------------------------------------------------ Suggestion to address all above comments: 1. allocate a bunch of pa...

..., > > So the PFNs of pages allocated may be across a large range, we will > > tell the host once the pfn_max -pfn_min >= 0x40000(1GB range), so the > > requests count is most likely to be more than 3. > > > > > > Now: > > > > total inflating time: 338ms > > > > the count of virtio data transmission: 373 > > > > > > Why was this so high? I would expect 3 transmissions. > > > > I follow your suggestion: > > ---------------------------------------------------------------------- > > --------------...

..., > > So the PFNs of pages allocated may be across a large range, we will > > tell the host once the pfn_max -pfn_min >= 0x40000(1GB range), so the > > requests count is most likely to be more than 3. > > > > > > Now: > > > > total inflating time: 338ms > > > > the count of virtio data transmission: 373 > > > > > > Why was this so high? I would expect 3 transmissions. > > > > I follow your suggestion: > > ---------------------------------------------------------------------- > > --------------...

...> > I have measured the performance when using a 32K page bitmap, Just to make sure. Do you mean a 32Kbyte bitmap? Covering 1Gbyte of memory? > and inflate the balloon to 3GB > of an idle guest with 4GB RAM. Should take 3 requests then, right? > Now: > total inflating time: 338ms > the count of virtio data transmission: 373 Why was this so high? I would expect 3 transmissions. > the call count of madvise: 865 > > before: > total inflating time: 175ms > the count of virtio data transmission: 1 > the call count of madvise: 42 > > Maybe the resu...

...tor.service - Network UPS Tools - power device monitor and shutdown controller Loaded: loaded (/lib/systemd/system/nut-monitor.service; enabled; preset: enabled) Active: active (running) since Fri 2024-01-19 03:37:28 CET; 1h 41min ago Main PID: 847 (upsmon) Tasks: 2 (limit: 38253) Memory: 3.4M CPU: 338ms CGroup: /system.slice/nut-monitor.service ??847 /lib/nut/upsmon -F ??849 /lib/nut/upsmon -F Jan 19 03:43:08 servername nut-monitor[849]: UPS Eaton at localhost on battery Jan 19 03:43:09 servername nut-monitor[916]: Network UPS Tools upsmon 2.8.0 Jan 19 03:43:33 servername nut-monitor[849]: UPS Eat...

...f pages allocated may be across a large range, we will > > > tell the host once the pfn_max -pfn_min >= 0x40000(1GB range), so the > > > requests count is most likely to be more than 3. > > > > > > > > Now: > > > > > total inflating time: 338ms > > > > > the count of virtio data transmission: 373 > > > > > > > > Why was this so high? I would expect 3 transmissions. > > > > > > I follow your suggestion: > > > -----------------------------------------------------------------...

...device monitor and > shutdown controller > Loaded: loaded (/lib/systemd/system/nut-monitor.service; enabled; > preset: enabled) > Active: active (running) since Fri 2024-01-19 03:37:28 CET; 1h 41min ago > Main PID: 847 (upsmon) > Tasks: 2 (limit: 38253) > Memory: 3.4M > CPU: 338ms > CGroup: /system.slice/nut-monitor.service > ??847 /lib/nut/upsmon -F > ??849 /lib/nut/upsmon -F > Jan 19 03:43:08 servername nut-monitor[849]: UPS Eaton at localhost on > battery > Jan 19 03:43:09 servername nut-monitor[916]: Network UPS Tools upsmon 2.8.0 > Jan 19 03:43:33 s...

...ating page in balloon driver, > So the PFNs of pages allocated may be across a large range, we will > tell the host once the pfn_max -pfn_min >= 0x40000(1GB range), > so the requests count is most likely to be more than 3. > > > > Now: > > > total inflating time: 338ms > > > the count of virtio data transmission: 373 > > > > Why was this so high? I would expect 3 transmissions. > > I follow your suggestion: > ------------------------------------------------------------------------------------ > Suggestion to address all above c...

...down controller >> Loaded: loaded (/lib/systemd/system/nut-monitor.service; enabled; >> preset: enabled) >> Active: active (running) since Fri 2024-01-19 03:37:28 CET; 1h 41min ago >> Main PID: 847 (upsmon) >> Tasks: 2 (limit: 38253) >> Memory: 3.4M >> CPU: 338ms >> CGroup: /system.slice/nut-monitor.service >> ??847 /lib/nut/upsmon -F >> ??849 /lib/nut/upsmon -F >> Jan 19 03:43:08 servername nut-monitor[849]: UPS Eaton at localhost on >> battery >> Jan 19 03:43:09 servername nut-monitor[916]: Network UPS Tools upsmon 2.8....

...d: loaded (/lib/systemd/system/nut-monitor.service; enabled; > >> preset: enabled) > >> Active: active (running) since Fri 2024-01-19 03:37:28 CET; 1h 41min ago > >> Main PID: 847 (upsmon) > >> Tasks: 2 (limit: 38253) > >> Memory: 3.4M > >> CPU: 338ms > >> CGroup: /system.slice/nut-monitor.service > >> ??847 /lib/nut/upsmon -F > >> ??849 /lib/nut/upsmon -F > >> Jan 19 03:43:08 servername nut-monitor[849]: UPS Eaton at localhost on > >> battery > >> Jan 19 03:43:09 servername nut-monitor[916]:...

...system/nut-monitor.service; enabled; >> >> preset: enabled) >> >> Active: active (running) since Fri 2024-01-19 03:37:28 CET; 1h 41min ago >> >> Main PID: 847 (upsmon) >> >> Tasks: 2 (limit: 38253) >> >> Memory: 3.4M >> >> CPU: 338ms >> >> CGroup: /system.slice/nut-monitor.service >> >> ??847 /lib/nut/upsmon -F >> >> ??849 /lib/nut/upsmon -F >> >> Jan 19 03:43:08 servername nut-monitor[849]: UPS Eaton at localhost on >> >> battery >> >> Jan 19 03:43:09 serv...

...ce; enabled; >>> >> preset: enabled) >>> >> Active: active (running) since Fri 2024-01-19 03:37:28 CET; 1h 41min ago >>> >> Main PID: 847 (upsmon) >>> >> Tasks: 2 (limit: 38253) >>> >> Memory: 3.4M >>> >> CPU: 338ms >>> >> CGroup: /system.slice/nut-monitor.service >>> >> ??847 /lib/nut/upsmon -F >>> >> ??849 /lib/nut/upsmon -F >>> >> Jan 19 03:43:08 servername nut-monitor[849]: UPS Eaton at localhost on >>> >> battery >>> >&...

...>> preset: enabled) > >>> >> Active: active (running) since Fri 2024-01-19 03:37:28 CET; 1h 41min ago > >>> >> Main PID: 847 (upsmon) > >>> >> Tasks: 2 (limit: 38253) > >>> >> Memory: 3.4M > >>> >> CPU: 338ms > >>> >> CGroup: /system.slice/nut-monitor.service > >>> >> ??847 /lib/nut/upsmon -F > >>> >> ??849 /lib/nut/upsmon -F > >>> >> Jan 19 03:43:08 servername nut-monitor[849]: UPS Eaton at localhost on > >>> >> b...

> On Fri, May 20, 2016 at 05:59:46PM +0800, Liang Li wrote: > > The implementation of the current virtio-balloon is not very > > efficient, Bellow is test result of time spends on inflating the > > balloon to 3GB of a 4GB idle guest: > > > > a. allocating pages (6.5%, 103ms) > > b. sending PFNs to host (68.3%, 787ms) c. address translation (6.1%, > >

> On Fri, May 20, 2016 at 05:59:46PM +0800, Liang Li wrote: > > The implementation of the current virtio-balloon is not very > > efficient, Bellow is test result of time spends on inflating the > > balloon to 3GB of a 4GB idle guest: > > > > a. allocating pages (6.5%, 103ms) > > b. sending PFNs to host (68.3%, 787ms) c. address translation (6.1%, > >