> gst-device-monitor-1.0.exe
...
Device found:
name : 00 Pro Capture AIO
class : Video/Source
RDBMS-based job queues have been criticized recently for being unable to handle heavy loads. And they deserve it, to some extent, because the queries used to safely lock a job have been pretty hairy. SELECT FOR UPDATE followed by an UPDATE works fine at first, but then you add more workers, and each is trying to SELECT FOR UPDATE the same row (and maybe throwing NOWAIT in there, then catching the errors and retrying), and things slow down.
On top of that, they have to actually update the row to mark it as locked, so the rest of your workers are sitting there waiting while one of them propagates its lock to disk (and the disks of however many servers you're replicating to). QueueClassic got some mileage out of the novel idea of randomly picking a row near the front of the queue to lock, but I can't still seem to get more than an an extra few hundred jobs per second out of it under heavy load.
So, many developers have started going straight t
#!/bin/bash | |
echo "arc_stats::print -a arcstat_p.value.ui64" | mdb -kw > value.ui64 | |
ui64=$(cat value.ui64) | |
echo "${ui64:0:16}/Z 0x10000000" | mdb -kw | |
echo "arc_stats::print -a arcstat_c.value.ui64" | mdb -kw > value.ui64 | |
ui64=$(cat value.ui64) | |
echo "${ui64:0:16}/Z 0x10000000" | mdb -kw | |
echo "arc_stats::print -a arcstat_c_max.value.ui64" | mdb -kw > value.ui64 | |
ui64=$(cat value.ui64) | |
echo "${ui64:0:16}/Z 0x10000000" | mdb -kw |
#!/bin/bash | |
echo "arc_stats::print -a arcstat_p.value.ui64" | mdb -kw > value.ui64 | |
ui64=$(cat value.ui64) | |
echo "${ui64:0:16}/Z 0x10000000" | mdb -kw | |
echo "arc_stats::print -a arcstat_c.value.ui64" | mdb -kw > value.ui64 | |
ui64=$(cat value.ui64) | |
echo "${ui64:0:16}/Z 0x10000000" | mdb -kw | |
echo "arc_stats::print -a arcstat_c_max.value.ui64" | mdb -kw > value.ui64 | |
ui64=$(cat value.ui64) | |
echo "${ui64:0:16}/Z 0x10000000" | mdb -kw |
I hereby claim:
- I am matthiasg on github.
- I am matthiasg (https://keybase.io/matthiasg) on keybase.
- I have a public key ASCFZyamXEDIBolEyLgrbvdB36vrCF5jFywJG0tmR1hdCAo
To claim this, I am signing this object:
struct MyType { | |
value: u32 | |
} | |
impl MyType { | |
fn new() -> MyType { | |
MyType { | |
value: 1 | |
} | |
} |
// From: https://github.com/Hartland/GPL-CPU-Miner/blob/master/sha2.c | |
if ("undefined" == typeof vnet) { | |
vnet = new Array(); | |
} | |
if ("undefined" == typeof vnet.crypt) { | |
vnet.crypt = new Array(); | |
} |
[root@smartos ~]# UUID="afe2f552-4a35-4c44-8855-a9bac10f27d2" | |
[root@smartos ~]# vmadm update ${UUID} qemu_extra_opts="-chardev socket,path=/tmp/vm.qga,server,nowait,id=qga0 -device virtio-serial -device virtserialport,chardev=qga0,name=org.qemu.guest_agent.0" | |
Successfully updated VM afe2f552-4a35-4c44-8855-a9bac10f27d2 | |
[root@smartos ~]# vmadm boot ${UUID} | |
Successfully started VM afe2f552-4a35-4c44-8855-a9bac10f27d2 | |
[root@smartos ~]# sleep 60 # Machine needs to boot up | |
[root@smartos ~]# echo '{"execute": "guest-ping" }' | socat stdio unix-connect:/zones/${UUID}/root/tmp/vm.qga # Is GA alive? | |
{"return": {}} | |
[root@smartos ~]# echo '{"execute": "guest-info" }' | socat stdio unix-connect:/zones/${UUID}/root/tmp/vm.qga # show information about GA | |
{"return": {"version": "0.12.1", "supported_commands": [{"enabled": true, "name": "guest-set-vcpus"}, {"enabled": true, "name": "guest-get-vcpus"}, {"enabled": true, "name": "guest-network-get-interfaces"}, {"enabled": true, "name": "guest-suspend-hybrid"}, {"enabled": tru |