Seed up build process

[Damon Snyder]

If all you are doing is redirects what about the possibility of putting
nginx in front of varnish to do that portion of the request? I would
imagine that HUP'ing nginx would be a lot faster for this kind of thing.

Damon


On Tue, Feb 12, 2013 at 2:47 AM, Tobias Eichelbrönner <
tobias.eichelbroenner at lamp-solutions.de> wrote:

> Hi,
>
> I have got plenty of vcl code mainly containing redirect information for
> hundreds of domains.
>
> All together there are about 34 MB of vcl text files containing 70000
> rules for redirection. Varnish generates about 158MB c-code out of it,
> that is compiled into a 90MB shared object.
>
> My problem is, that it takes more than one and a half hour to parse the
> vcl code into c-code and than compiling it on an Intel Xeon W3530.
>
> Does anyone has an idea how to speed up the process?
> Is there for example a possibility to tell the parser to pass any
> optimization steps while generating the c code?
>
> I could store all information in a database and call it in realtime, but
> that would cause heavy IO on the database.
>
> Sincerely,
>
> Tobias
>
> _______________________________________________
> varnish-misc mailing list
> varnish-misc at varnish-cache.org
> https://www.varnish-cache.org/lists/mailman/listinfo/varnish-misc
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://www.varnish-cache.org/lists/pipermail/varnish-misc/attachments/20130214/1659d3da/attachment.html>