NexentaStor 1.0.5 (Default branch)


 
Thread Tools Search this Thread
Special Forums News, Links, Events and Announcements Software Releases - RSS News NexentaStor 1.0.5 (Default branch)
# 1  
Old 07-29-2008
NexentaStor 1.0.5 (Default branch)

Image NexentaStor leverages the ZFS file system and is optimized for use in 2nd-tier NAS and iSCSI applications requiring open, low cost, high performance storage as well as dramatically simplified provisioning, expansion, backup, replication, and archiving. It is also used as a primary NAS in businesses that wish to expand at closer to commodity pricing. It supports unlimited snapshots, snapshot mirroring (replication), block level mirroring, integrated search, and easy management of extremely large storage pools. License: Other/Proprietary License with Free Trial Changes:
Advanced Plugin Infrastructure and the first pluggable modules, including auto-cdp, I/O benchmark, and network utilization. iSCSI Target Zvol has support for advanced hierarchy. iSCSI target portal groups. Rsync protocol version 30 support. Remote Storage Appliance API (SA-API) is documented. Bindings are available for C, C++, Perl, Python, and Ruby. NMC 'help keyword' has been added.Image

More...
Login or Register to Ask a Question

Previous Thread | Next Thread
Login or Register to Ask a Question
max_thread_proc(5)						File Formats Manual						max_thread_proc(5)

NAME
max_thread_proc - defines the maximum number of concurrent threads allowed per process. VALUES
Failsafe Default Allowed values Recommended values DESCRIPTION
is a dynamic tunable that limits the maximum number of threads allowed per process on the system. When tuning the maximum number of threads allowed per process will be the new value of No process will be able to create new threads such that the total count of its threads exceeds Who is Expected to Change This Tunable? System administrators that run applications on their systems requiring a high number of threads per process. Restrictions on Changing The effect of tuning on existing processes is undefined. However, existing threads will not be effected. When Should the Value of This Tunable Be Raised? The value of should be raised if there is a need to run an application that requires a higher number of threads per process than what is currently set to accommodate. Also, if thread creation fails with the value of then it could indicate that the has been reached. However, reaching is not the only reason why a thread creation could fail with may be returned if the system tunable has been reached or memory on the system is exhausted. What Are the Side Effects of Raising the Value? A group of processes may be able to exhaust the system wide limit of threads on the system. When Should the Value of This Tunable Be Lowered? If you feel that it is necessary to limit the number of threads allowed per process. What Are the Side Effects of Lowering the Value? Some applications which need a high number of threads may behave differently or fail to operate. What Other Tunable Values Should Be Changed at the Same Time? You may want to look at the value of 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
nkthread(5). Tunable Kernel Parameters max_thread_proc(5)