28%
07.06.2019
predecessor. PHP developers will notice this especially with invalid patterns. Furthermore, PCRE2 is based on Unicode version 10.0 instead of Unicode 7.0. In PHP 7.3, the preg_quote() function now also masks
28%
11.04.2016
RProxyExtensions = css, gif, html, jpg, js, png, txt
CacheSize = 25 #mb
CacheMaxFilesize = 128 #kb
##load tinkering
#ListenBacklog = 128 #default 16
#MaxServerLoad = 0.7 #drop on high load (eeks)
#Socket
28%
07.01.2014
the space used in the two backup directories and the SOURCE
directory. The SOURCE
directory reports using 9.2MB; backup.0
, the most recent snapshot, also reports using 9.2MB (as it should), and backup.1
28%
08.06.2021
was used. The performance with Legate is about 100 times that of regular Python and NumPy.
Finally, I can try running the code with Legate and the GPU:
$ legate --gpus 1 --fbmem 3000 test1_legate.py
[0
28%
14.11.2013
of the virtual computer models; their hardware configurations follow on the right. For example, the computer named m1.small only has one CPU and 256MB of RAM. The free/max column is also interesting: The number
28%
30.05.2021
the following:
$ gpustat -P
[0] Tesla V100-SXM2-16GB | 37'C, 0 %, 24 / 300 W | 0 / 16160 MB |
One GPU is present, running at a cool 37 Celsius and drawing 24W while doing absolutely nothing. To proceed further
28%
17.02.2015
://developer.nvidia.com/jetson-tk1
Odroid-XU3
Android 4.4, Linux
Samsung Exynos5422
Quad ARM Cortex-A15 @2.0GHz (32KB/32KB/2MB), Quad ARM Cortex-A7 @1.4GHz (32KB/32KB/512KB)
Mali-T628 MP6
28%
14.06.2017
on /home/laytonjb/squashfs/20170502.sqsh, block size 131072.
[================================================-] 2904/2904 100%
Exportable Squashfs 4.0 filesystem, gzip compressed, data block size 131072
compressed
28%
14.08.2017
/laytonjb/squashfs/20170502.sqsh
Parallel mksquashfs: Using 4 processors
Creating 4.0 filesystem on /home/laytonjb/squashfs/20170502.sqsh, block size 131072.
[================================================-] 2904/2904 100
28%
07.07.2015
a “single security issue classified as high severity.” The security problem apparently does not affect OpenSSL versions 1.0.0 or 0.9.8, but users of other OpenSSL versions should prepare to upgrade as soon
