trafficserver-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Muhammad Faisal" <>
Subject Re: Different Cache Disk for different size of objects
Date Mon, 21 Mar 2016 18:34:33 GMT
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 

Some folks has done some tweaks with squid refer to below link:


------ Original Message ------
From: "Reindl Harald" <>
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 
>>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" < <>>
>><>; "Muhammad Faisal"
>>< <>>
>>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 <
>>>><>> wrote:
>>>>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 
>>>before you get the response. And at that point, you (currently) can’t
>>>move to a different storage / volume. But @amc would know best

View raw message