search for: usage

...I will find my target audience here. We are looking to hire a consultant to help us figure out an issue. We are having what seems are "random load" issues with bare metal boxes that are dedicated to Asterisk and a few Perl AGI's. We went after all the usual suspects (CPU IDLE, memory usage etc.). I wrote the simple bash script below to show me total calls and CPU usage of Asterisk #! /bin/bash for i in {1..50} do CALLS=$(asterisk -rx'core show calls' | head -n 1 | awk '{print $1}') CPU=$(top -b -n 1 | grep $(pidof asterisk) | awk '{print $9}')...

...script to check out the packet queue (with the help of https://serverfault.com/questions/623377/is-there-a-way-to-get-current-txqueue-utilization-on-e-g-eth0-or-tun-device) and it *seems there may be a corelation between packets in the queue and the load on Asterisk [root at a30 ~]# /tmp/x.sh CPU USAGE 393.8 Active calls 317 CPU USAGE 117.6 Active calls 318 CPU USAGE 143.8 Active calls 318 CPU USAGE 305.9 Active calls 318 udp 0 768 0.0.0.0:14510 0.0.0.0:* CPU USAGE 123.5 Active calls 316 CPU USAGE 137.5 Active calls 314 CPU USAGE 329.4 Active calls 314 CPU USAGE 312.5 Active...

...ber of vertex blend matrices: 0 - Max vertex textures: 4 - Vertex textures shared: no * Render to Vertex Buffer : no * DirectX per stage constants: no DefaultWorkQueue('Root') initialising on thread main. Particle Renderer Type 'billboard' registered fixme:d3d:resource_check_usage Unhandled usage flags 0x8. fixme:d3d:resource_check_usage Unhandled usage flags 0x8. fixme:d3d:resource_check_usage Unhandled usage flags 0x8. fixme:d3d:resource_check_usage Unhandled usage flags 0x8. fixme:d3d:resource_check_usage Unhandled usage flags 0x8. fixme:d3d:resource_check_usage Unhandled...

..._locator_ConnectServer 0xccf1538, L"\\\\.\\root\\cimv2", (null), (null), (null), 0x00000000, (null), (nil), 0x32f858) fixme:wbemprox:wbem_locator_ConnectServer 0xccf1538, L"\\\\.\\root\\cimv2", (null), (null), (null), 0x00000000, (null), (nil), 0x32f858) fixme:d3d:resource_check_usage Unhandled usage flags 0x8. fixme:d3d:resource_check_usage Unhandled usage flags 0x8. fixme:d3d:resource_check_usage Unhandled usage flags 0x8. fixme:d3d:resource_check_usage Unhandled usage flags 0x8. fixme:d3d:resource_check_usage Unhandled usage flags 0x8. fixme:d3d:resource_check_usage Unhandled...

...->(0x10028,00000113) fixme:win:WIN_CreateWindowEx Parent is HWND_MESSAGE dummy fixme:d3d:IWineD3DDeviceImpl_CreateSurface Trying to create a render target that isn't in the default pool fixme:d3d_surface:IWineD3DSurfaceImpl_UnlockRect unsupported unlocking to Rendering surface surf@0x19a1250 usage(WINED3DUSAGE_RENDERTARGET) sqpoldir: SetDirName[c:\Program Files\PlayOnline\SquareEnix\PlayOnlineViewer\] polBackToGameFlag =0 g_bNeedToGetAllMsg =1 CSettingFileDirectory -----> "c:\Program Files\PlayOnline\SquareEnix\PlayOnlineViewer\usr\all\" fixme:d3d:IWineD3DDeviceImpl_CreateSurfac...

...t queue (with the help of > https://serverfault.com/questions/623377/is-there-a-way-to-get-current-txqueue-utilization-on-e-g-eth0-or-tun-device) > and it *seems there may be a corelation between packets in the queue and > the load on Asterisk > > [root at a30 ~]# /tmp/x.sh > CPU USAGE 393.8 Active calls 317 > CPU USAGE 117.6 Active calls 318 > CPU USAGE 143.8 Active calls 318 > CPU USAGE 305.9 Active calls 318 > udp 0 768 0.0.0.0:14510 0.0.0.0:* > > CPU USAGE 123.5 Active calls 316 > CPU USAGE 137.5 Active calls 314 > CPU USAGE 329.4 A...

...39;t have access to it at the moment. However, I still have a dump of a tokenized version of the descriptor (one line for each main, local, or global item). It won't be useful to you for testing, but at least you might be able to read it to see what the source of the bug was. Namely, the "usage" for feature 35 is given twice. It is a strange report descriptor, but not technically wrong, and apparently several APC models send a descriptor like this. ====================================================================== This example shows the effect of the HIDParser bug (before and af...

Signed-off-by: Simon COURTOIS <scourtois at linagora.com> --- src/app/controllers/usages_controller.rb | 13 +++++++ src/app/models/usage.rb | 2 +- src/app/services/usage_service.rb | 23 ++++++++++++ src/app/views/network/_form.rhtml | 56 +++++++++++++++++++++++++++++- src/config/routes.rb | 1 + src/public/stylesheets/...

...ri2 (e.g. in the working case). Doing a diff between a log of starting gnome-shell with dri vs dri3 results in this: --- mesa.log.dri2 2015-08-10 14:18:03.182712022 +0200 +++ mesa.log.dri3 2015-08-10 14:18:33.233336338 +0200 @@ -1,8 +1,8 @@ nv30_miptree_create 512x32 uniform_pitch 0 usage 0 flags 0 -nv30_miptree_from_handle 1x1 uniform_pitch 1024 usage 0 flags 0 +nv30_miptree_create 1x1 uniform_pitch 0 usage 0 flags 0 nv30_miptree_create 1x1 uniform_pitch 0 usage 0 flags 0 nv30_miptree_create 512x32 uniform_pitch 0 usage 0 flags 0 -nv30_miptree_from_handle 1x1 uniform_pitch 1024...

...bug_d3dformat Unrecognized 0x5a534552 (as fourcc: RESZ) WINED3DFORMAT! fixme:d3d:wined3d_get_format Can't find format unrecognized (0x5a534552) in the format lookup table fixme:d3d:swapchain_init Add OpenGL context recreation support to context_validate_onscreen_formats fixme:d3d:resource_check_usage Unhandled usage flags 0x8. fixme:d3d:resource_check_usage Unhandled usage flags 0x8. fixme:d3d:resource_check_usage Unhandled usage flags 0x8. fixme:d3d:resource_check_usage Unhandled usage flags 0x8. fixme:d3d:resource_check_usage Unhandled usage flags 0x8. fixme:d3d:resource_check_usage Unhandled...

...xit(bar()); foo() } +#foo() # now simple "infinite recursion" +# +# +#> ## bad infinite recursion / on.exit / ... interactions +#> bar <- function() 1+1 +#> foo <- function() { on.exit(bar()); foo() } +#> foo() # now simple "infinite recursion" +#Error: C stack usage is too close to the limit +#Error: C stack usage is too close to the limit +#Error: C stack usage is too close to the limit +#Error: C stack usage is too close to the limit +#Error: C stack usage is too close to the limit +#Error: segfault from C stack overflow +#Error: C stack usage is too close t...

...riptorType 33 bcdHID 1.10 bCountryCode 0 Not supported bNumDescriptors 1 bDescriptorType 34 Report wDescriptorLength 618 Report Descriptor: (length is 618) Item(Global): Usage Page, data= [ 0x84 ] 132 Power Device Page Item(Local ): Usage, data= [ 0x04 ] 4 UPS Item(Main ): Collection, data= [ 0x01 ] 1 Application Item(Local ): Usage, data= [ 0x24...

...bDescriptorType 33 bcdHID 1.10 bCountryCode 0 Not supported bNumDescriptors 1 bDescriptorType 34 Report wDescriptorLength 447 Report Descriptor: (length is 447) Item(Global): Usage Page, data= [ 0x84 ] 132 Power Device Page Item(Local ): Usage, data= [ 0x04 ] 4 UPS Item(Main ): Collection, data= [ 0x01 ] 1 Application Item(Local ): Usage, data= [ 0x24 ] 36...

...W Unimplemented action: 59 (SPI_SETSTICKYKEYS) fixme:system:SystemParametersInfoW Unimplemented action: 51 (SPI_SETFILTERKEYS) fixme:system:SystemParametersInfoW Unimplemented action: 53 (SPI_SETTOGGLEKEYS) fixme:win:EnumDisplayDevicesW ((null),0,0x33ef5c,0x00000000), stub! fixme:d3d:resource_check_usage Unhandled usage flags 0x28. fixme:d3d:resource_check_usage Unhandled usage flags 0x8. fixme:d3d:resource_check_usage Unhandled usage flags 0x20. fixme:d3d:resource_check_usage Unhandled usage flags 0x8. fixme:d3d:wined3d_swapchain_set_gamma_ramp Ignoring flags 0x1. err:ole:CoInitializeEx Attempt to...

...n% names(formals(base::apply))) do something else do something else Unfortunately, I cannot conditionalize the man pages of the functions. I get the message that "applySpeclib.Rd:12-14: Section \Sexpr is unrecognized and will be dropped" if I try to dynamically define the entire usage section. If I try to use \Sexpr inside the \usage section, I get the following warning: "applySpeclib.Rd:13-15: Tag \Sexpr is invalid in a \usage block" Does anybody have an idea how to proceed. The full code is available below. Thanks Lukas *1. Code for full usage section:* .. \d...

On Sun, 7 Jun 2015, Charles Lepple wrote: > [please use reply-all to include the list, as the list does not override the Reply-To header.] > > On Jun 7, 2015, at 5:02 PM, Greg Hersch <hersch.greg at gmail.com> wrote: > >> Here is the driver debug log. If I just let it run, it pops up with >> libusb_get_string_invalid argument over and over again, mixed in the

...nit The application requested more than one back buffer, this is not properly supported. Please configure the application to use double buffering (1 back buffer) if possible. fixme:d3d:swapchain_init Add OpenGL context recreation support to context_validate_onscreen_formats fixme:d3d:resource_check_usage Unhandled usage flags 0x8. fixme:d3d:resource_check_usage Unhandled usage flags 0x8. fixme:d3d:resource_check_usage Unhandled usage flags 0x8. fixme:d3d:resource_check_usage Unhandled usage flags 0x8. fixme:d3d:resource_check_usage Unhandled usage flags 0x8. fixme:d3d:resource_check_usage Unhandled...

...en Swallow, and > during testing, LiveRanges seemed to be consuming one of the largest > chunks of memory. I wrote a replacement allocator for use by > BumpPtrAllocator which uses mmap()/munmap() in place of > malloc()/free(). It has worked flawlessly in testing, and reduces > memory usage quite nicely in Unladen Swallow. > > The code is available for review here. I'd appreciate feedback if > there's an interest in integrating this into LLVM trunk: > http://codereview.uplinklabs.net/1905049 > > Here are the results of our memory utilization tests. The '...

...memory reduction in Unladen Swallow, and during testing, LiveRanges seemed to be consuming one of the largest chunks of memory. I wrote a replacement allocator for use by BumpPtrAllocator which uses mmap()/munmap() in place of malloc()/free(). It has worked flawlessly in testing, and reduces memory usage quite nicely in Unladen Swallow. The code is available for review here. I'd appreciate feedback if there's an interest in integrating this into LLVM trunk: http://codereview.uplinklabs.net/1905049 Here are the results of our memory utilization tests. The 'Mem max' numbers aren'...

...d just completely implement the official USB HID UPS spec. That way no subdriver would be needed, or at least very little. At the moment, we use USB VID and PID to select which HID-to-NUT tables to consult (since some vendors have "custom" (incorrect) interpretations of standard HID PDC Usages. So at the very least, you would need a skeleton usbhid-ups subdriver which matches your VID:PID combination. From there, though, if you follow the standard HID PDC Usage IDs, you should be able to just map the "HID path" (see below) to the corresponding NUT name. > However, I am ha...