Sponsored Content
Top Forums UNIX for Beginners Questions & Answers Should I use a CoW filesystem on my PC if I only wanted snapshot capabilities ? Post 303045038 by stomp on Wednesday 11th of March 2020 05:28:50 AM
Old 03-11-2020
Two more comments on zfs:
  • Don't fill up the filesystems
    If you fill up zfs file systems above 80%, performance will degrade.
  • No manual balancing method available
    If you have a Volume with more than one vdev and they are not equally full performance also degrades. For best performance vdev utilization should be equal of every vdev. But there are times when vdev utilization is completely different. For example if you add a new vdev: The new vdev will be empty. There are 2 typical ways to solve that:
    • utilization will slowly level to the pool average over time
      The percentage of the probability for a vdev to be the targe for a new write is the reversed percentage of the utilization of that vdev. So the least filled up vdev will get more new data as the other ones and the vdev utilization will average with writes and deletes over time.
    • export and import the zfs pool
      If you like to have it immediately, you may export and import the pool. That way on the import all data will be distributed evenly over all vdevs. That task of course needs a lot of temporary space and probably time when you have quite some TB of data.

Regarding the performance of filesystems, I'm interested in it quite much. Right now, I'm writing benchmark scripts testing different aspects of it and will open a thread here soon.
 

9 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Unix Capabilities?

We are looking into buying a new software, billing software that is, and want to know if you can run that on the same UNIX server as another major software? Is there a limit to the different types of software Unix can run, or is it like windows where you can install as many as you like? ... (2 Replies)
Discussion started by: hoz
2 Replies

2. UNIX for Advanced & Expert Users

p570 Capabilities

Hi there. I've been tasked with making a new design for our Unix systems :eek: Now the question I have is; How many LPARs can a p570 hold WITHOUT using a VIO Server. Many Thanks Kees (1 Reply)
Discussion started by: KeesH
1 Replies

3. Red Hat

Adding capabilities to an RPM

Hi. I downloaded a package that could only be installed on RHEL5, and not 4 or 3, so I got the source in order to compile it on RHEL 3 so hopefully it will work on all versions. So I have the source for a working package, but when I build it in RHEL 3 and then try to install it in RHEL 5, it... (6 Replies)
Discussion started by: Boaz
6 Replies

4. Filesystems, Disks and Memory

Wanted: Geographically distributed filesystem solution

I'm looking for a means to ensure that servers in the two or three datacenters, connected in a ring via IP through two ISPs, can distribute load and/or replicate data among at least two SAN-class disk devices. I want to evaluate several solutions, and I'm open to solutions ranging from free,... (6 Replies)
Discussion started by: otheus
6 Replies

5. Solaris

Cannot use filesystem while sending a snapshot

I've got a Solaris 11 Express installed on my machine. I have created a raidz2 zpool named shares and a simple one-disc zpool named backup. I have made a script that would send a daily snapshot of shares to backup. I use these commands zfs snapshot shares@DDMMRRRRHHMM zfs send -i shares@....... (10 Replies)
Discussion started by: RychnD
10 Replies

6. UNIX for Advanced & Expert Users

Use of Capabilities

I wonder if anyone could assist with some problems I'm having with Linux Capabilities and their use when using the commands "nice" and "schedtool". I run a couple of PCs, one is an elderly AMD Sempron 2800+ (32-bit, 2GHz clock and 3GB memory) that is used as a family multimedia system running... (3 Replies)
Discussion started by: MikeGM
3 Replies

7. Linux

Broadcom under Fedora 18 (Spherical Cow)

So I'm having a problem getting a Broadcom BCM4312 wireless controller to work under the broadcom-wl module $uname Linux 3.8.11-200.fc18.x86_64 #1 SMP Wed May 1 19:44:27 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux lspci -v 05:00.0 Network controller: Broadcom Corporation BCM4312 802.11b/g... (2 Replies)
Discussion started by: Skrynesaver
2 Replies

8. UNIX for Advanced & Expert Users

Linux capabilities discussion

Hi I'm trying to compile my linux kernel with CONFIG_SECURITY_CAPABILITIES=y. any idea what this thing does ?? Also another question , If I compile the kernel that I'm currently using , what'll happen ? ~cheers (3 Replies)
Discussion started by: leghorn
3 Replies

9. What is on Your Mind?

Anybody want to talk about Dirty Cow?

Hi All, How worried is everyone about the Dirty Cow Linux exploit? Has anybody experienced attacks yet? From the research I've done it seems that the exploit is "reliable" (that is it works nearly every time on vulverable systems) which is not good news. We all believe that Unix/Linux... (3 Replies)
Discussion started by: hicksd8
3 Replies
aio_monitor_run_sec(5)						File Formats Manual					    aio_monitor_run_sec(5)

NAME
aio_monitor_run_sec - frequency of AIO thread pool monitor execution (in seconds) VALUES
Failsafe Default Allowed values Recommended values DESCRIPTION
The implementation of POSIX AIO on HP-UX uses kernel threads to perform I/Os to filesystems that do not directly support true asynchronous I/O. (This distinction is transparent to the user.) The kernel threads are organized into worker-thread pools (called AIO thread pools) created on a per-process basis. Since a thread pool mechanism for I/Os introduces a variety of trade-offs concerning utilization of CPU time vs. I/O resources, four dynamic tunables are available to customize the behavior of this thread pool: and Please see individual man- pages for details on each of these tunables. The tunable specifies how frequently a process' AIO thread pool will be monitored. Monitoring involves making decisions about growing or shrinking the AIO thread pool based on the constraints specified by and Note that although the AIO thread pool can grow both on its own (as new I/Os are issued) or as a result of the monitoring mechanism, the monitoring mechanism is the primary method by which the thread pool can shrink. So this tunable effectively determines how quickly the AIO thread pool will adapt itself to a given I/O load. Who Is Expected to Change This Tunable? System administrators that run applications requiring heavy usage of POSIX AIO to filesystems. Restrictions on Changing This tunable is dynamic. Changes to to this tunable take effect immediately for new processes started after the change. They also impact existing processes, but the speed with which the changes propagate to running processes is determined by the former value of When Should the Value of This Tunable Be Raised? should be raised for applications that have steady I/O loads for which POSIX AIO would rarely need to adapt. Another possibility is appli- cations with bursty or periodic I/O loads, that want POSIX AIO to maintain a larger thread pool through periods of decreased I/O activity (to be ready for busier periods). This can be accomplished by increasing this tunable to reduce the frequency of AIO monitor updates. What Are the Side Effects of Raising the Value of This Tunable? Increasing this tunable will reduce the speed with which the POSIX AIO thread pool mechanism adapts itself to changing I/O loads. This could cause slightly reduced performance when applications first begin to issue POSIX AIOs. When Should the Value of This Tunable Be Lowered? should be lowered when applications want to increase the speed with which the POSIX AIO thread pool adapts itself to I/O loads. This should generally maximize performance, except in the case of bursty I/O loads, or I/O loads with periodic peaks, for which a slower adapta- tion may be desirable. What Are the Side Effects of Lowering the Value of This Tunable? The POSIX AIO thread pool will adjust more quickly to changing I/O loads, so new threads will be spawned more quickly for new I/Os, and threads will be killed more quickly as I/O loads decrease. Except for bursty or periodic I/O loads, this should maximize performance. What Other Tunables Should Be Changed at the Same Time as This One? interacts with this tunable by setting a strict limit on the number of threads that can be used for POSIX AIO. interacts with this tunable by setting a limit on the number of threads that can be used for POSIX_AIO, but does so based on a percentage of the maximum number of allowable process threads. This allows the AIO thread pools to respond dynamically to changes in defines the desired relationship between the number of POSIX AIO kernel threads and the number of I/Os to be serviced. WARNINGS
All HP-UX kernel tunable parameters are release specific. This parameter may be removed or have its meaning changed in future releases of HP-UX. Installation of optional kernel software, from HP or other vendors, may cause changes to tunable parameter values. After installation, some tunable parameters may no longer be at the default or recommended values. For information about the effects of installation on tun- able values, consult the documentation for the kernel software being installed. For information about optional kernel software that was factory installed on your system, see at AUTHOR
was developed by HP. SEE ALSO
kctune(1M), sam(1M), gettune(2), settune(2), aio_proc_threads(5), aio_proc_thread_pct(5), aio_req_per_thread(5). Tunable Kernel Parameters aio_monitor_run_sec(5)
All times are GMT -4. The time now is 04:41 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy