-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Hello all,
I searched for a bit but can't really find any advice on this problem.
I'm in the conceptual phase of a new bot but it requires a bit of processing. Unfortunately the only way this processing can be done is by writing out two small files.
However, the processing should be very fast, and after it's done the files can be trashed. For that reason, I don't think it's very logical to tax the hard drive with this processing.
Instead I was hoping to find a small RAM disk on toolserver that I could use which would act like a file system without the hard drive performance issues. Unfortunately, I didn't find one.
Is there (a) a RAM disk-like option on the toolserver, (b) a way to request that one be made, or (c) a reason I shouldn't even bother looking into this and just use real files instead?
Thanks for any input, - -- Shirik
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Matthew P. Del Buono:
I'm in the conceptual phase of a new bot but it requires a bit of processing. Unfortunately the only way this processing can be done is by writing out two small files.
However, the processing should be very fast, and after it's done the files can be trashed. For that reason, I don't think it's very logical to tax the hard drive with this processing.
You can use /tmp, which is a memory filesystem for exactly this reason. (But only on Solaris systems, not Linux, so you probably want to use willow.)
- river.
Or /dev/shm/ on linux.
-Cobi On Nov 14, 2010 9:58 AM, "River Tarnell" river.tarnell@wikimedia.de wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Matthew P. Del Buono:
I'm in the conceptual phase of a new bot but it requires a bit of processing. Unfortunately the only way this processing can be done is by writing out two small files.
However, the processing should be very fast, and after it's done the files can be trashed. For that reason, I don't think it's very logical to tax the hard drive with this processing.
You can use /tmp, which is a memory filesystem for exactly this reason.
(But
only on Solaris systems, not Linux, so you probably want to use willow.)
- river.
-----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.16 (FreeBSD)
iEYEARECAAYFAkzf+P4ACgkQIXd7fCuc5vIFkwCfXhsetFTLJJvVYVerAKE4jNG3 wfcAnAoFiazNtySfumKsAPeygwOeqpA/ =EVqn -----END PGP SIGNATURE-----
Toolserver-l mailing list (Toolserver-l@lists.wikimedia.org) https://lists.wikimedia.org/mailman/listinfo/toolserver-l Posting guidelines for this list:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
You can use /tmp, which is a memory filesystem for exactly this reason. (But only on Solaris systems, not Linux, so you probably want to use willow.)
Thanks river, I saw /tmp but assumed it was mounted on a drive.
Regards, - -- Shirik
On 14/11/2010 1:36 PM, Matthew P. Del Buono wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
You can use /tmp, which is a memory filesystem for exactly this reason. (But only on Solaris systems, not Linux, so you probably want to use willow.)
Wait, why isn't your /tmp be mounted with tmpfs? (Hm. Debian/Ubuntu only mount /var/run on tmpfs by default; that might be it). No reason for it not to be, really.
-- Coren / Marc
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Marc A. Pelletier:
You can use /tmp, which is a memory filesystem for exactly this reason. (But only on Solaris systems, not Linux, so you probably want to use willow.)
Wait, why isn't your /tmp be mounted with tmpfs? (Hm. Debian/Ubuntu only mount /var/run on tmpfs by default; that might be it). No reason for it not to be, really.
/tmp is tmpfs on Solaris because it's the default on that platform. It's not on Linux because it's not the default there (at least not on Debian). Since we haven't observed that file i/o on /tmp contributes to any kind of performance issue, it was not worth the trouble to change it.
- river.
toolserver-l@lists.wikimedia.org