Lines Matching +full:swap +full:- +full:size +full:- +full:gb

31 .Sh SYSTEM SETUP - DISKLABEL, NEWFS, TUNEFS, SWAP
32 The swap partition should typically be approximately 2x the size of
34 for systems with less than 4GB of RAM, or approximately equal to
35 the size of main memory
38 expansion when sizing the swap partition.
39 Configuring too little swap can lead
43 with multiple disks, configure swap on each drive.
44 The swap partitions on the drives should be approximately the same size.
46 internal data structures scale to 4 times the largest swap partition.
48 the swap partitions near the same size will allow the kernel to optimally
49 stripe swap space across the N disks.
51 little, swap space is the saving grace of
53 and even if you do not normally use much swap, it can give you more time to
63 partitions are read-mostly, with very little writing, while
68 heavily write-loaded partitions will not bleed over into the mostly-read
81 .Dq Li "tunefs -n enable /filesystem" .
82 Softupdates drastically improves meta-data performance, mainly file
103 A number of run-time
117 file systems normally update the last-accessed time of a file or
138 atime turned on for mostly read-only partitions such as
161 or essentially read-only partitions such as
168 Choosing the proper stripe size is also
170 File systems tend to store meta-data on power-of-2 boundaries
173 means you want to use a large off-center stripe size such as 1152 sectors
174 so sequential I/O does not seek both disks and so meta-data is distributed
179 run-time.
194 The virtual memory system always does accounting of the swap space
195 reservation, both total for system and per-user.
236 to fall back to using double-copy.
249 of internal memory management page-tracking overhead at the cost of wiring
268 the minimum in-core memory used to cache a directory is the physical page
269 size (typically 4K) rather than 512 bytes.
270 We recommend turning this option off in memory-constrained environments;
292 disk controllers system-wide at any given time.
294 The default is self-tuned and
298 controllers or drives with average IO size used in production works
309 sysctl governs VFS read-ahead and is expressed as the number of blocks
310 to pre-read if the heuristics algorithm decides that the reads are
313 With the default UFS block size of 32 KiB, a setting of 64 will allow
319 read-ahead adversely affects performance or where system memory is really
340 There are various other buffer-cache and VM page cache related sysctls.
363 You can adjust the buffer size for incoming and outgoing data separately.
369 can be used to introduce route-specific send and receive buffer size
392 These extensions should be enabled and the TCP buffer size should be set
395 high-latency satellite links.
438 slightly delay the teardown of a connection, or slightly delay the ramp-up
439 of a slow-start TCP connection.
442 turning off delayed acks may be referring to the slow-start issue.
475 may block large ranges of ports (usually low-numbered ports) and expect systems
483 sysctl limits the size of the listen queue for accepting new TCP connections.
489 may itself limit the listen queue size (e.g.,\&
492 often have a directive in its configuration file to adjust the queue size up.
501 thousand if you are running databases or large descriptor-heavy daemons.
502 The read-only
518 the system, and may be determined at run-time by inspecting the value of the
519 read-only
527 tunables set the default soft limits for process data and stack size
536 tunables set the hard limits for process data, stack, and text size
564 lead to a boot-time crash.
591 a large-scale system.
602 and drivers you do not have will reduce the size of your kernel, sometimes
626 will be able to better use higher-end CPU features for MMU, task switching,
628 Additionally, higher-end CPUs support
639 is paging to swap a lot you need to consider adding more memory.