Mailing-List: contact users-help@trafficserver.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@trafficserver.apache.org
From: "Muhammad Faisal" <faisalusuf@yahoo.com>
To: users@trafficserver.apache.org, users@trafficserver.apache.org
Subject: Re: Different Cache Disk for different size of objects
Date: Mon, 21 Mar 2016 18:34:33 +0000
Message-Id: <em629ccb85-9f77-4360-a3af-5d41b9da8bf8@augere-1>
In-Reply-To: <56F03BAC.1010305@thelounge.net>
Reply-To: "Muhammad Faisal" <faisalusuf@yahoo.com>
User-Agent: eM_Client/6.0.24928.0
Mime-Version: 1.0
Content-Type: text/plain; format=flowed; charset=utf-8
Content-Transfer-Encoding: quoted-printable

Not memory, one way could be that ATS know the type of storage it has,=20
use SSD as temp storage later move large objects to HDD (least recently=20
used object for e.g) via separate ATS thread/process. I dont why how=20
this will impact the overall system but this can complement RAM Cache=20
performance.

Some folks has done some tweaks with squid refer to below link:
http://www.squid-cache.org/mail-archive/squid-users/201208/0284.html

--
Regards,
Faisal.


------ Original Message ------
From: "Reindl Harald" <h.reindl@thelounge.net>
To: users@trafficserver.apache.org
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=20
>>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=20
>the meantime until you know where to store? buffer it in memory?
>
>>------ Original Message ------
>>From: "Leif Hedstrom" <zwoop@apache.org <mailto:zwoop@apache.org>>
>>To: users@trafficserver.apache.org
>><mailto:users@trafficserver.apache.org>; "Muhammad Faisal"
>><faisalusuf@yahoo.com <mailto:faisalusuf@yahoo.com>>
>>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 <faisalusuf@yahoo.com
>>>><mailto:faisalusuf@yahoo.com>> 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 =E2=80=9Cstor=
age=E2=80=9D
>>>before going to origin, so you don=E2=80=99t know what the size is going=
 to=20
>>>be
>>>before you get the response. And at that point, you (currently) can=E2=
=80=99t
>>>move to a different storage / volume. But @amc would know best
>