Re: solid-state drives

2012-08-02 Thread Sven Gaerner
On Wed, Aug 01, 2012 at 06:16:13PM -0400, Pierre Abbat wrote:
 This is a spinoff of the Aleutia question, since Aleutia puts SSDs in 
 computers. How does the periodic Hammer job handle SSDs? Does reblocking do 
 anything different than on an HDD? If a computer has an SSD and an HDD, which 
 should get the swap space?
 
 Pierre

On my workstation I use an SSD for the root filesystem, swapcache and
/usr/pkg.

The current configuration has snapshots set to 1d (10d retention time)
and reblocking is set to 7d (1m runtime). All other option (prune,
rebalance, dedup and recopy) are disabled.

Currently it is running fine, but in my opinion running swapcache on a
workstation that just runs for a couple of hours is not always
necessary. I'm just running this setup to play with the swapcache and
the SSD, because I think it is a very nice feature.

Regards,
Sven



Re: solid-state drives

2012-08-02 Thread Matthew Dillon

:On Wed, Aug 01, 2012 at 06:16:13PM -0400, Pierre Abbat wrote:
: This is a spinoff of the Aleutia question, since Aleutia puts SSDs in 
: computers. How does the periodic Hammer job handle SSDs? Does reblocking do 
: anything different than on an HDD? If a computer has an SSD and an HDD, 
which 
: should get the swap space?
: 
: Pierre
:
:On my workstation I use an SSD for the root filesystem, swapcache and
:/usr/pkg.
:
:The current configuration has snapshots set to 1d (10d retention time)
:and reblocking is set to 7d (1m runtime). All other option (prune,
:rebalance, dedup and recopy) are disabled.
:
:Currently it is running fine, but in my opinion running swapcache on a
:workstation that just runs for a couple of hours is not always
:necessary. I'm just running this setup to play with the swapcache and
:the SSD, because I think it is a very nice feature.
:
:Regards,
:Sven

You will definitely want to turn pruning on, it doesn't do all that much
I/O and its needed to clean up the fine-grained snapshots.  Rebalance,
dedup, and recopy can be left turned off.

-Matt
Matthew Dillon 
dil...@backplane.com


Re: frequency scaling on D525MW not working properly

2012-08-02 Thread Matthew Dillon
Also on the D5* atoms on FreeBSD it would be nice to check that it
actually works as advertised, by running a few cpu-bound processes
(i.e. for (;;); ) and measuring the watts being burned at different
frequencies.  That's the real proof that the frequency scaling is doing
something real.

-Matt


Re: frequency scaling on D525MW not working properly

2012-08-02 Thread Sepherosa Ziehau
On Fri, Aug 3, 2012 at 2:00 AM, Sven Gaerner sgaer...@gmx.net wrote:
 On Tue, Jul 31, 2012 at 09:27:15AM +0800, Sepherosa Ziehau wrote:
 On Tue, Jul 31, 2012 at 5:01 AM, Sven Gaerner sgaer...@gmx.net wrote:
 [...]

 Hmm, maybe i8254 is not working at all.  Could you post following 
 information:
 - bootverbose dmesg w/ hw.i8254.intr_disable=0 in /boot/loader.conf
 - sysctl kern.cputimer
 - sysctl hw.acpi

 Attached the requested details.

Grrr, only C1 is detected.  If the CPU does support C3, there could be
some settings in BIOS?

Best Regards,
sephe

-- 
Tomorrow Will Never Die