trafficserver-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Randeep <randeep...@gmail.com>
Subject Re: using RAMDISK with ats
Date Mon, 25 Jul 2016 09:43:45 GMT
Thank you Leif, James and Steve.

I don't have any issue using RAMdisk with tmpfs mounting as directory. I
was asking whether it is right thing to do.

Best regards,
Randeep

On Sun, Jul 24, 2016 at 6:37 PM, Steve Malenfant <smalenfant@gmail.com>
wrote:

> Look into the Traffic Control CDN project. They have figured that one out
> with the ramdisk block devices. As far as I can tell, it should be the
> following :
>
> - Set the proper ramdisk_size in the kernel boot line to create big enough
> ramdisk block devices
> - Put as many devices you need in the storage.config. You can have a
> single ram_disk or multiple just like disk volume. Ex: "/dev/ram0 volume=2"
> - Modify the permission to allow ats to read/write from the block devices
> (using udev, if you are not running as root).
> - Reboot server
>
> Steve
>
> On Sun, Jul 24, 2016 at 3:50 AM, James Peach <jpeach@apache.org> wrote:
>
>>
>> > On Jul 24, 2016, at 4:21 PM, Randeep <randeep123@gmail.com> wrote:
>> >
>> > Thank you James.
>> >
>> > Is there any specific way do you recommend using ramdisk? As raw device?
>>
>> Like I just said, you can’t use tmpfs as a block device. I believe you
>> can use ramdisk as a block device but I haven’t tried it; you should go
>> read the kernel documentation on that.
>>
>> Like I showed below, tmpfs seems to work fine. Mayb you have some other
>> problem?
>>
>> >
>> > Regards,
>> > Randeep
>> >
>> > On Sun, Jul 24, 2016 at 11:48 AM, James Peach <jpeach@apache.org>
>> wrote:
>> >
>> >>
>> >>> On Jul 24, 2016, at 2:18 PM, Randeep <randeep123@gmail.com> wrote:
>> >>>
>> >>> Hi all,
>> >>>
>> >>> I am trying to use RAMdisk for ats.
>> >>>
>> >>> Here is how I created RAMDISK
>> >>> *mount -o size=20G -t tmpfs none /mnt/ramdisk/*
>> >>>
>> >>> And in storage.config I have specified it as below.
>> >>> cat /opt/ats/etc/trafficserver/storage.config
>> >>> /mnt/ramdisk* 20G*
>> >>>
>> >>> But every time I restart ats, I get the following warning.
>> >>> [Jul 23 21:15:28.334] Server {0x2b9a5aba6380} WARNING: <Store.cc:528
>> >>> (init)> not enough free space for cache directory '/mnt/ramdisk’
>> >>
>> >> I did a quick test and tmpfs doesn’t support any of the ioctl methods
>> that
>> >> we use to determine the block device size and IO parameters so you
>> won’t be
>> >> able to use this as a raw device.
>> >>
>> >> Adding it as a directory seems to work just fine…
>> >>
>> >> [root@fedora-23 trafficserver]# cat
>> >> /opt/ats/etc/trafficserver/storage.config
>> >> /mnt/ramdisk 20G
>> >>
>> >> [root@fedora-23 trafficserver]# ls -lh /mnt/ramdisk
>> >> total 26M
>> >> -rw-r--r-- 1 nobody nobody 20G Jul 23 23:15 cache.db
>> >>
>> >>> My question is, what is the right way to create ramdisk for ats and
>> how
>> >> we
>> >>> need to specify it in the storage.config. (with or without size?)
>> >>>
>> >>> I checked in the documentation also. It doesn't have any information
>> >>> regarding ramdisk. It would be great if someone can add it.
>> >>>
>> >>> --
>> >>> Randeep
>> >>> Mob: +919447831699[kerala]
>> >>> Mob: +919880050349[B'lore]
>> >>> http://twitter.com/Randeeppr
>> >>> http://in.linkedin.com/in/randeeppr
>> >>>
>> >>>
>> >>> [image: --]
>> >>> Randeep Raman
>> >>> [image: http://]about.me/Randeeppr
>> >>> <http://about.me/Randeeppr>
>> >>
>> >>
>> >
>> >
>> > --
>> > Randeep
>> > Mob: +919447831699[kerala]
>> > Mob: +919880050349[B'lore]
>> > http://twitter.com/Randeeppr
>> > http://in.linkedin.com/in/randeeppr
>> >
>> >
>> > [image: --]
>> > Randeep Raman
>> > [image: http://]about.me/Randeeppr
>> > <http://about.me/Randeeppr>
>>
>>
>


-- 
Randeep
Mob: +919447831699[kerala]
Mob: +919880050349[B'lore]
http://twitter.com/Randeeppr
http://in.linkedin.com/in/randeeppr


[image: --]
Randeep Raman
[image: http://]about.me/Randeeppr
<http://about.me/Randeeppr>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message