24%
23.03.2022
-34-1804/72
/dev/loop7 17441 17441 0 100% /snap/gnome-3-38-2004/87
/dev/nvme1n1p1 62513152 7087560 55425592 12% /home
/dev/nvme0n1p1 0 0 0 - /boot/efi
/dev/loop8 17495 17495 0
24%
07.11.2011
#pragma omp parallel for shared (sum) private (i)
12 for ( i=0; i < 1000000; i++) {
13 #pragma omp critical (sum_total)
14 sum = sum + a[i];
15 }
16 printf("sum=%lf\n",sum);
17
24%
05.08.2024
catatonit conmon containernetworking-plugins crun golang-github-containers-common
golang-github-containers-image netavark passt podman
0 upgraded, 11 newly installed, 0 to remove and 0 not upgraded.
Need to get 32.3 MB of archives.
After this operation, 131 MB
24%
07.11.2011
GB)
03 Socket P#0
04 Core L#0 + PU L#0 (P#0)
05 Core L#1 + PU L#1 (P#2)
06 Core L#2 + PU L#2 (P#4)
07 Core L#3 + PU L#3 (P#6)
08 NUMANode P#1 (12GB)
09 Socket P#1
10
24%
01.08.2019
CREATED SIZE
nginx f09fe80eb0e7 12 days ago 109MB
nginx latest 35640fed495c 12 days ago 109MB
Backdoor Access
Considering how well Docker Scan handled
24%
07.02.2019
data copy(a)
!$acc parallel loop
do i=1,n
a(i) = 0.0
enddo
!$acc data end
#pragma acc data copy(a)
{
#pragma acc parallel loop
{
for (int i=0; i < n; i++)
{
a[i] = 0.0
24%
27.09.2021
-ready
With the top command in the other terminal window, you can watch the MicroK8s processes running. My device showed a one-minute average load of between 3.0 and 3.5, even with Docker running dutifully ... A zero-ops installation of Kubernetes with MicroK8s operates on almost no compute capacity and roughly 700MB of RAM.
24%
29.06.2012
Item(bottom_func,(),false,(thunk(AST(lambda({},{{#1, #2}, {{#1, Any, 2}, {#2, Any, 2}}, {}},
begin
#1 = top(Array)(top(Any),2)
top(arrayset)(#1,1,"n0")
top(arrayset)(#1,2,"n2")
#2 = #1
return addprocs_ssh(#2)
end
))),1),(),(),intset(1
24%
29.09.2020
-amd64.tar.gz.sha256sum
[...snip]
e6be589df85076108c33e12e60cfb85dcd82c5d756a6f6ebc8de0ee505c9fd4c helm-v3.1.2-linux-amd64.tar.gz
$ sha256sum helm-v3.1.2-linux-amd64.tar.gz
e6be589df85076108c33e12e60cfb85
24%
21.01.2021
. The initial processor speed was 300MHz. Future processors used 450, 600, and even 675MHz. Similar to the T3D, the T3E could scale from 8 to 2,176 PEs, and each PE had between 64MB and 2GB of memory. The T3D