Login | Register For Free | Help
Search for: (Advanced)

Mailing List Archive: Varnish: Misc

Few questions regarding varnish with FreeBSD

 

 

Varnish misc RSS feed   Index | Next | Previous | View Threaded


nicole4pt at gmail

Apr 24, 2012, 2:50 PM

Post #1 of 3 (354 views)
Permalink
Few questions regarding varnish with FreeBSD

Hello, I have a few questions about using varnish on FreeBSD

1) Is it better to use malloc or to create a memory disk?


2) Any idea why a FreeBSD server running varnish takes forever to shutdown
or restart if rebooted?
When performing say a shutdown -r now / -h now The system will stay at
"All Buffers Synced" once I let it run and it took an hour to finally
reach Uptime: TIME / The operating system has halted.(for -h)


3) I have a cache server with 3 disks 135 gigs ea and 4 Gigs ram. The
disks are only 8G full ea.
Why would my n_lru_nuked (381451 ) be so high?

I understand this to be "The number of objects varnish has had to evict
from cache before they expired to make room for other content" Why would
this happen when I still have so much room?



Thanks for any help

Thanks

Nicole


phk at phk

Apr 24, 2012, 2:55 PM

Post #2 of 3 (341 views)
Permalink
Re: Few questions regarding varnish with FreeBSD [In reply to]

In message <CAEJj9Cw0X2A2s=oAA_0MN9h4TYH14qYBUJPKE8CBdc5dR80MQA [at] mail>, "Nicole H." writes:

>1) Is it better to use malloc or to create a memory disk?

Malloc is better.

>2) Any idea why a FreeBSD server running varnish takes forever to shutdown
>or restart if rebooted?
> When performing say a shutdown -r now / -h now The system will stay at
>"All Buffers Synced" once I let it run and it took an hour to finally
>reach Uptime: TIME / The operating system has halted.(for -h)

Interesting, havn't seen that one before.

What happens if you run the "sync" command before shutdown ?

>3) I have a cache server with 3 disks 135 gigs ea and 4 Gigs ram. The
>disks are only 8G full ea.
> Why would my n_lru_nuked (381451 ) be so high?

If this is a 32bit system, you are limited by the 32bit address space
and Varnish can probably only get about 3GB of address space for caching.


--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
phk [at] FreeBSD | TCP/IP since RFC 956
FreeBSD committer | BSD since 4.3-tahoe
Never attribute to malice what can adequately be explained by incompetence.

_______________________________________________
varnish-misc mailing list
varnish-misc [at] varnish-cache
https://www.varnish-cache.org/lists/mailman/listinfo/varnish-misc


nicole4pt at gmail

Apr 25, 2012, 2:15 PM

Post #3 of 3 (355 views)
Permalink
Re: Few questions regarding varnish with FreeBSD [In reply to]

On Tue, Apr 24, 2012 at 2:55 PM, Poul-Henning Kamp <phk [at] phk>wrote:

> In message <CAEJj9Cw0X2A2s=
> oAA_0MN9h4TYH14qYBUJPKE8CBdc5dR80MQA [at] mail>, "Nicole H." writes:
>
> >1) Is it better to use malloc or to create a memory disk?
>
> Malloc is better.
>
>
Thanks


> >2) Any idea why a FreeBSD server running varnish takes forever to shutdown
> >or restart if rebooted?
> > When performing say a shutdown -r now / -h now The system will stay at
> >"All Buffers Synced" once I let it run and it took an hour to finally
> >reach Uptime: TIME / The operating system has halted.(for -h)
>
> Interesting, havn't seen that one before.
>
> What happens if you run the "sync" command before shutdown ?
>
>
I have tried that to no avail. This occurs on systems running FreeBSD 8.X
and 9.0.

Syslogd: exiting on signal 15
Waiting (max 60 seconds) for system process 'vnlru' to stop... done
Waiting (max 60 seconds) for system process 'bufdaemon' to stop... done

Waiting (max 60 seconds) for system process 'syncer' to stop...Syncing
disks, vnodes remaining...2 2 2 1 1 0 0 0 done
All buffers synced.

And that's where it will stay for a very very long time.
Is there a way to find out what its hanging on? What is left for the
server to do after that point?

----

Another other odd thing is when it boots back up, it says
Starting varnishd
WARNING: (-sfile) file size reduced to 86100456243 (80% of available disk
space)
WARNING: (-sfile) file size reduced to 86100456243 (80% of available disk
space)
WARNING: (-sfile) file size reduced to 86100456243 (80% of available disk
space)

Each disk is 135Gigs formatted. Each shows 24G of space used via df or
only 19% Capacity.
They are mounted ufs, local, noatime, soft-updates (I know soft updates
don't help but they were already there)
They are dedicated for use by varnish.

However rc.conf settings are varnishd_storage="file,/
cache1/varnish-cache.bin,65%"
( I added other entries for a varnish_storage2 and 3)
There is no malloc storage on this particular server since there is only 4G
of RAM. I have tried adding some but it did not seem to make any difference.

So why does it say reduced to 80%?



> >3) I have a cache server with 3 disks 135 gigs ea and 4 Gigs ram. The
> >disks are only 8G full ea.
> > Why would my n_lru_nuked (381451 ) be so high?
>
> If this is a 32bit system, you are limited by the 32bit address space
> and Varnish can probably only get about 3GB of address space for caching.
>
>
It's running 64 bit software.
I basically took a few servers that we had been running squid on and tried
running Varnish. Squid reverse proxy always did fine and never seemed to
push the systems resources.
Is it because its limited by the 4gigs of ram or by the number of
objects? How can I tell how many objects are stored?




Thanks!

Nicole






>
> --
> Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
> phk [at] FreeBSD | TCP/IP since RFC 956
> FreeBSD committer | BSD since 4.3-tahoe
> Never attribute to malice what can adequately be explained by incompetence.
>



--
---
Nicole Melody Harrington - UNIX Systems Mistress
admin1 [at] picturetrail -- http://www.picturetrail.com
Obey or the button gets it!

Varnish misc RSS feed   Index | Next | Previous | View Threaded
 
 


Interested in having your list archived? Contact Gossamer Threads
 
  Web Applications & Managed Hosting Powered by Gossamer Threads Inc.