17%
18.12.2013
(One-by-One)
1 #include
2
3 /* Our structure */
4 struct rec
5 {
6 int x,y,z;
7 float value;
8 };
9
10 int main()
11 {
12 int counter;
13 struct rec my_record;
14 int counter_limit;
15
17%
19.05.2014
, eight with HyperThreading, running at 3.5GHz)
32GB of memory (DDR3-1600)
GigE NIC
Simple GigE switch
CentOS 6.5 (updates current as of March 29, 2014)
The test system that mounts
17%
10.06.2014
"ram": 2048,
07 "resolvers": ["192.168.111.254"],
08 "disks": [
09 {
10 "image_uuid": "1fc068b0-13b0-11e2-9f4e-2f3f6a96d9bc",
11 "boot": true,
12 "model": "virtio"
13 }
14
17%
12.11.2012
@trapper:~\$ "
send -- "ssh aspen\r"
expect -exact "ssh aspen\r
khess@aspen’s password: "
send -- "PASSWORD\r"
expect -exact "\r
Linux aspen 2.6.32-43-server #97-Ubuntu SMP Wed Sep 5 16:56:41 UTC 2012 x86_64 GNU
17%
04.11.2011
testing on a test cluster, because the production systems are 100% identical.
Partimage [2] is an easy-to-use imaging tool that backs up and restores different types of partitions. SystemImager [3] is far
17%
07.11.2011
Python code designed with threading is to use the built-in multiprocessing
package included in Python from version 2.6 on. This package provides an API similar to the threading
Python module. Although
17%
06.08.2012
-07-28 19:06 .bash_history
-rw-r--r-- 1 khess khess 220 2012-05-25 22:11 .bash_logout
-rw-r--r-- 1 khess khess 2940 2012-05-25 22:11 .bashrc
To show files in date-sorted order, try the following commands
17%
25.01.2017
-dimensional arrays.
If the array is local to the image, you access the array as you normally would. For example, for image 3 to access element (2,2)
from the array, the statement would be something like:
b ... Modern Fortran – Part 3
17%
18.10.2017
a000)
libpgc.so => /opt/pgi/linux86-64/16.10/lib/libpgc.so (0x00007f5bc4fc2000)
librt.so.1 => /lib64/librt.so.1 (0x00007f5bc4dba000)
libm.so.6 => /lib64/libm.so.6 (0x00007f5bc4
17%
16.07.2019
is spent compiling the function. Recall that the first pass through the code compiles it. Subsequent passes do not:
CPU times: user 72.3 ms, sys: 8 µs, total: 72.3 ms
Wall time: 72 ms
Notice that the run
