Noted Reindl!
--
------ Original Message ------
From: "Reindl Harald" <[email protected]>
To: [email protected]
Sent: 3/22/2016 1:39:55 AM
Subject: Re: Different Cache Disk for different size of objects
Am 21.03.2016 um 19:34 schrieb Muhammad Faisal:
Not memory, one way could be that ATS know the type of storage it has,
use SSD as temp storage later move large objects to HDD (least
recently
used object for e.g) via separate ATS thread/process. I dont why how
this will impact the overall system but this can complement RAM Cache
performance.
sorry, but that's nonsense
you *surely* don't want GB of data stored on SSD and then move to
rotating disks and wear out SSD that way
KISS - Keep It Simple Stupid!
Some folks has done some tweaks with squid refer to below link:
http://www.squid-cache.org/mail-archive/squid-users/201208/0284.html
------ Original Message ------
From: "Reindl Harald" <[email protected]>
To: [email protected]
Sent: 3/21/2016 11:21:32 PM
Subject: Re: Different Cache Disk for different size of objects
Am 21.03.2016 um 19:19 schrieb Muhammad Faisal:
OK. But this feature can be added right? May be in future releases.
It can improve caching performance by avoiding seek time of disks
which
increase over the period of time with high disk WR.
but what do you are doing with a 2 GB reponse without a size header
in
the meantime until you know where to store? buffer it in memory?
------ Original Message ------
From: "Leif Hedstrom" <[email protected] <mailto:[email protected]>>
To: [email protected]
<mailto:[email protected]>; "Muhammad Faisal"
<[email protected] <mailto:[email protected]>>
Sent: 3/21/2016 9:52:35 PM
Subject: Re: Different Cache Disk for different size of objects
On Mar 18, 2016, at 3:35 AM, Muhammad Faisal <[email protected]
<mailto:[email protected]>> wrote:
Hi,
Is this possible to allocate a different disk for different object
sizes? Below is the scenario I'm trying to implement:
Object size <1MB -----> SSD
Object Size > 1MB ----> HDD
This will improve Caching performance as smaller objects will be
served from SSD while larger objects will reside on the HDD.
No, not at this point. Part of the issue is that we select
“storage”
before going to origin, so you don’t know what the size is going to
be
before you get the response. And at that point, you (currently)
can’t
move to a different storage / volume. But @amc would know best
--
Reindl Harald
the lounge interactive design GmbH
A-1060 Vienna, Hofmühlgasse 17
CTO / CISO / Software-Development
m: +43 (676) 40 221 40, p: +43 (1) 595 3999 33
icq: 154546673, http://www.thelounge.net/
http://www.thelounge.net/signature.asc.what.htm
