18%
20.03.2014
as PaaS
GigaSpaces, the company behind Cloudify, began developing the tool in 2012. Cloudify was originally designed as a tool for Platform-as-a-Service (PaaS) applications (although the boundaries to SaaS
18%
16.05.2013
optionally provide file services with its own virtual file server, NTVFS (necessitating a filesystem with XATTR support) or the embedded Samba 3 file server, S3FS.
Best practices suggest separating file
18%
14.11.2013
Controller
login2$ ls -s /sys/devices/system/edac/mc/mc0
total 0
0 ce_count 0 csrow1 0 csrow4 0 csrow7 0 reset_counters 0 size_mb
0 ce_noinfo_count 0 csrow2 0 csrow5 0 device 0 sdram
18%
08.10.2015
Applications are no longer only developed and run on local machines. In the cloud era, this also takes place in virtual cloud environments. Such platform as a service (PaaS) environments offer many
18%
16.05.2013
has no effect on the SSD's performance.
Common consumer 7,200rpm disk drives can achieve sustained data transfer rates around 1Gbps and can comfortably operate within the established SATA 3Gbps
18%
01.04.2014
as PaaS
GigaSpaces, the company behind Cloudify, began developing the tool in 2012. Cloudify was originally designed as a tool for Platform-as-a-Service (PaaS) applications (although the boundaries to SaaS
18%
28.08.2013
that does exactly this. A Ruby version also does something very similar.
Compression Tools
A data compression tool also is commonly used. Typically it’s used to compress files that aren’t used often
18%
17.09.2013
:
login2$ /sbin/lsmod
...
sb_edac 12898 0
edac_core 46773 3 sb_edac
...
EDAC was loaded as a module, so I examined the directory /sys/devices/system/edac
:
login2$ ls -s /sys/devices/system/edac/
total 0
18%
13.06.2022
) for a class B problem size.
Therefore, I will run the EP, FT, and MG tests to check health performance. For class B, the EP test takes 5.46s, the FT test 17.26s, and the MB test 3.8s. If I stay with only
18%
14.11.2013
applies to the operation of an instance of the CDB and not for the PDBs.
Some simple math can help clarify this concept: For example, 10 databases in version 11g need at least 10x350MB, or around 3.5GB
