Nor does UFS. I'm not sure of your point.
Regardless, this issue seems to have far too many gaps in the information provided by the OP to assist.
Cheers
IIRC, UFS does use swap and you have to decide ahead of time how to organize partitions. I got tired of that, which prompted my move to ZFS. My point in this thread is, ZFS is your friend in surprising ways ( less likelihood of page thrashing when OP is using MySQL, for example).
What do you mean?
The installer will definitely suggest a swap partition for a default disk layout if you pick UFS instead of ZFS. If you pay attention to the Handbook, particularly Section 2.6, Allocating Disk Space, Section 2.6.2, Guided Partitioning Using UFS, Figure 15 (Review Created Partitions) clearly shows a swap partition for the UFS option.
That sounds like an extraordinarily long time, which suggests you have an extraordinarily large import. Am I right in thinking the import file is produced by a logical backup tool such as mysqldump? I don't know much about your use case, but if so, have you considered using a physical backup tool e.g. Percona's xtrabackup / innobackupex? These backups would be smaller and faster to both produce and to restore.
I'm not the one who did the backup/restore though xtrabackup is often used. Import file was quite large, 750GB
Ah, that's what you meant.
Funny... in ZFS setups that are supposedly 'default', as in suggested by the installer, I haven't seen a single swap section. Not on mine, not on anyone else's. To see who provided examples, take a look at this thread:
OK, that's great. Just thought I should also mention mydumper - specifically the accompanying myloader program - as an alternative for restoring logical backups as it utilises multithreading which might speed things up a bit for you.
yeah, the link works, but there's also a [PORT][/PORT] tag (icon looks like gears): databases/mydumper. Just chiming in. I guess dbdemon forgot the 'databases/' part when using the tag.
innodb_flush_method=fsync