Re: [Erlyaws-list] 10,000 virtual hosts

[Alfred B. M. C. <ott...@hu...>]

On Wed, 09 Mar 2011 00:41:26 -0800 Claes Wikstrom <klacke@tail-
f.com> wrote:
>On 03/09/2011 05:37 AM, Alfred B. M. Cordero wrote:
>>
>> I have tried out revproxy but it didn't work for one host. Using
>> virtual hosts worked
>> in yaws.conf, the yaw script had to be modified to allow for 
>more
>> db tables.
>>
>> The other yaws.cnf settings are getting tuned since there was an
>> error
>> Max size cached bytes reached for server "virtual.host.com"
>> Those errors are still there. How can I modify the max_* options 
>to
>> work
>> so many virtuals?
>>
>> What is the limit on virtual hosts?
>
>I don't think anyone has every tried yaws for as many virthosts as 
>
>10000. It would work, but I think it's safe to say it's not 
>optimized
>for that number of virt hosts.
>
>When Yaws, has parsed the HTTP header, it grabs the Host: header
>and then searches for the correct virt host in a list. This is for
>every HTTP request, thus could certainly be optimized for this 
>large
>number of virt hosts. Should be fairly easy I think

Easy for me or you? I think you. 

>
>>
>> The startup and yaws --hup are very slow, is there a way to 
>speed
>> those up?
>>
>
>
>Strange, maybe it's the parsing of the large config file, but that 
>
>sounds actually strange. --hup will also re-read yaws.conf so 
>maybe
>that's it. Needs research to answer.

Also there is a log file for every virtual. 10000 is a lot of files 
into one place. Maybe it would help to create logs by reversing the 
virtual name and creating dir for each component of the virtual.

vamos.al.la.playa.es becomes
var/log/es/playa/la/al/vamos.log

or hash the name with base36 or md5
var/log/A121WHATEVER/vamos.al.la.playa.es.log