> > Hi!
> >
> > > > SSD or spinning drives ?
> > > >
> > > > > I have 3.6 Gb of RAM and 2 Gb of swap.
> > > >
> > > > Run top and check the state of ARC.
> > > > I think it needs much more RAM.
> > >
> > > I don't think it is a SSD (it has cylinders, sectors etc.).
> > > If you can tell me a way to check it I will be glad to do it.
> > > This is the output of diskinfo -v /dev/ada0 in case it answers the 
> > > question:
> > > /dev/ada0
> > > 512 # sectorsize
> > > 320072933376 # mediasize in bytes (298G)
> > > 625142448 # mediasize in sectors
> > > 4096 # stripesize
> > > 0 # stripeoffset
> > > 620181 # Cylinders according to firmware.
> > > 16 # Heads according to firmware.
> > > 63 # Sectors according to firmware.
> > > HGST HTS545032A7E680 # Disk descr.
> >
> > This is a HGST drive, spinning, no SSD.
> >
> > > TMA45DZG06UX8R # Disk ident.
> > > No # TRIM/UNMAP support
> > > 5400 # Rotation rate in RPM
> > > Not_Zoned # Zone Mode
> > > These are are lines of top's header (poudriere is building one of the 
> > > ports I think
> > > might be problematic):
> > > CPU: 32.8% user, 4.8% nice, 8.3% system, 0.5% interrupt, 53.5% idle
> > > Mem: 1200M Active, 332M Inact, 32M Laundry, 2084M Wired, 187M Free
> > > ARC: 1122M Total, 649M MFU, 323M MRU, 1371K Anon, 16M Header, 133M Other
> > > 401M Compressed, 1064M Uncompressed, 2.65:1 Ratio
> >
> > So, when it's slow during builds, it's most probably swapping.
>

I have found the real cause of most of the problems: it's ccache configuration.
I used the same cache of 15 Gb for the host (amd64) and for all jails (both 
amd64 and i386):
the i386 jails disliked it very much. Creating a new cache only for the i386 
jails
fixed the problems. Maybe I will have to make the cache smaller to avoid 
problems
in future, but for now it is almost empty and everything is fine.

Thanks everybody for your help.

Lorenzo Salvadore.
_______________________________________________
[email protected] mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "[email protected]"

Reply via email to