nitesh naik wrote:
Hi All,
Issues was with Disk I/O. I have used null cache dir and squid
response is much faster now.
cache_dir null /empty
Thanks everyone for your help.
Regards
Nitesh
Oh dear, I can't believe I overlooked this.
cache_dir aufs (linux) or diskd (FreeBSD) is likely to solv
Hi All,
Issues was with Disk I/O. I have used null cache dir and squid
response is much faster now.
cache_dir null /empty
Thanks everyone for your help.
Regards
Nitesh
On Tue, Nov 4, 2008 at 9:40 AM, nitesh naik <[EMAIL PROTECTED]> wrote:
> Does these Redirector statistics mean url rewrite he
Does these Redirector statistics mean url rewrite helper program is
slowing down squid response ? avg service time is 1550 msec.
Redirector Statistics:
program: /home/zdn/bin/redirect_parallel.pl
number running: 2 of 2
requests sent: 1069753
replies received: 1069752
queue length: 0
avg service ti
Not sure if url rewrite helper is slowing down process because via
cache manager interface it didn't show any connection back log. What
information I should look for in cache manager to find out the cause
of the slow serving of requests ?
Redirector Statistics:
program: /home/zdn/bin/redirect_para
Henrik / Amos,
Tried using these setting and I could see see delay in serving the
requests even for cached objects.
1225687535.330 5459 81.52.249.101 TCP_MEM_HIT/200 1475 GET
http://abc.xyz.com/3613/172/500/248/211/i5.js?z=9059 - NONE/-
application/x-javascript
1225687535.330 5614 81.52.249.1
On tor, 2008-10-30 at 19:50 +0530, nitesh naik wrote:
> url rewrite helper script works fine for few requests ( 100 req/sec )
> but slows down response as number of requests increase and it takes
> 10+ second to deliver the objects.
I'v run setups like this at more than thousand requests/s.
> Is
nitesh naik wrote:
Henrik,
url rewrite helper script works fine for few requests ( 100 req/sec )
but slows down response as number of requests increase and it takes
10+ second to deliver the objects.
Is there way to optimise it further ?
url_rewrite_program /home/zdn/bin/redirect_parallel.pl
Henrik,
url rewrite helper script works fine for few requests ( 100 req/sec )
but slows down response as number of requests increase and it takes
10+ second to deliver the objects.
Is there way to optimise it further ?
url_rewrite_program /home/zdn/bin/redirect_parallel.pl
url_rewrite_children
There was mistake on my part I should have used following script to
process concurrent requests. Its working properly now.
#!/usr/bin/perl -an
BEGIN { $|=1; }
$id = $F[0];
$url = $F[1];
$url =~ s/\?.*//;
print "$id $url\n";
next;
Regards
Nitesh
On Thu, Oct 30, 2008 at 12:15
Henrik,
With this approach I see that only one redirector process is being
used and requests are processed in serial order. This causes delay in
serving the objects and even response for cache object is slower.
I tried changing url_rewrite_concurrency to 1 but with this setting
squid is not cachi
See earlier response.
On mån, 2008-10-27 at 16:59 +0530, nitesh naik wrote:
> Henrik,
>
> What if I use following code ? logic is same as your program ?
>
>
> #!/usr/bin/perl
> $|=1;
> while (<>) {
> s|(.*)\?(.*$)|$1|;
> print;
> next;
> }
>
> Regards
> Nitesh
>
> On Mon, Oct 27, 200
Henrik,
What if I use following code ? logic is same as your program ?
#!/usr/bin/perl
$|=1;
while (<>) {
s|(.*)\?(.*$)|$1|;
print;
next;
}
Regards
Nitesh
On Mon, Oct 27, 2008 at 4:25 PM, Henrik Nordstrom
<[EMAIL PROTECTED]> wrote:
>
> Sorry, forgot the following important line in bot
Sorry, forgot the following important line in both
BEGIN { $|=1; }
should be inserted as the second line in each script (just after the #! line)
On mån, 2008-10-27 at 11:48 +0100, Henrik Nordstrom wrote:
> Example script removing query strings from any file ending in .ext:
>
> #!/usr/bin/perl
On mån, 2008-10-27 at 16:12 +0530, nitesh naik wrote:
> Henrik,
>
> Is this code capable for handling requests in parallel ?
It's capable to handle the concurrent helper mode yes. It doesn't
process requests in parallell, but you don't need to.
Regards
Henrik
signature.asc
Description: This is
On mån, 2008-10-27 at 14:57 +0530, Nitesh Naik wrote:
> Is there any sample code available for url rewriter helper which will
> process requests in parallel?
It doesn't need to process them in parallell unless you really need to
scale the rewrites on multiple CPUs or threads making callouts to ot
Henrik,
Is this code capable for handling requests in parallel ?
#!/usr/bin/perl
$|=1;
while (<>) {
s|(.*)\?(.*$)|$1|;
print;
}
Regards
Nitesh
On Mon, Oct 27, 2008 at 4:04 PM, Henrik Nordstrom
<[EMAIL PROTECTED]> wrote:
> On mån, 2008-10-27 at 10:11 +0100, Matus UHLAR - fantomas wrote
On mån, 2008-10-27 at 10:11 +0100, Matus UHLAR - fantomas wrote:
> > Write your own url rewriter helper. It's no more than a couple of lines
> > perl..
>
> shouldn't that be storeurl rewriter?
No, since the backend server is not interested in this dummy query
string an url rewriter is better.
Re
Henrik / Matus ,
For certain request we don't want client browser to look for object in
its cache and everything should be served fresh. CDN will determine
expire time for the object. Some of these objects doesn't send out
Last modified header. In our case it is not important to pass query
string
> On mån, 2008-10-27 at 12:30 +0530, nitesh naik wrote:
> > We use query string in each url for bursting cache at client end (
> > browser) hence its not important for us and it won't provide any
> > incorrect results. We already use similar configuration at CDN level.
On 27.10.08 10:09, Henrik No
On mån, 2008-10-27 at 12:30 +0530, nitesh naik wrote:
> We use query string in each url for bursting cache at client end (
> browser) hence its not important for us and it won't provide any
> incorrect results. We already use similar configuration at CDN level.
Why do you do this?
> Henrik sugge
We use query string in each url for bursting cache at client end (
browser) hence its not important for us and it won't provide any
incorrect results. We already use similar configuration at CDN level.
We are trying to add squid layer between origin and CDN to reduce the
load on our origin servers
On 25.10.08 12:40, Nitesh Naik wrote:
> Squid should give out same object for different query string.
> Basically it should strip query string and cache the object so that
> same object is delivered to the client browser for different query
> string.
Did you understand what I've said - that such m
Squid should give out same object for different query string.
Basically it should strip query string and cache the object so that
same object is delivered to the client browser for different query
string.
I used squirm which is better I could see some performance improvement
but I am getting erro
On fre, 2008-10-24 at 13:40 +0530, nitesh naik wrote:
> Is there way to ignore query string in url so that objects are cached
> without query string ? I am using external perl program to strip them query
> string from url which is slowing down response time. I have started 1500
> processes of red
On 24.10.08 13:40, nitesh naik wrote:
> Is there way to ignore query string in url so that objects are cached
> without query string ? I am using external perl program to strip them query
> string from url which is slowing down response time. I have started 1500
> processes of redirect program.
>
Hi All,
Is there way to ignore query string in url so that objects are cached
without query string ? I am using external perl program to strip them query
string from url which is slowing down response time. I have started 1500
processes of redirect program.
If I run squid without redirect progra
26 matches
Mail list logo
