×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
"Steinmetz, Paul" <PSteinmetz@xxxxxxxxxx> wrote on Sat, 20 Sep
2014 00:38:07 GMT:
Could this be due to 5913, 0 read cache?
Feature 5913 has 1.8 GB of write cache. However, if your SSDs
are in a single parity set, you won't be getting the best
possible performance out of them.
Is there anything else I'm missing?
As I said before there are many variables. I can't recall if
anyone has asked about expert cache being turned on for the
memory pool where the reorg jobs run.
As I said, without looking at PEX trace data and standard
collection services data, we can speculate and point at things
to look for but are unlikely to come up with the exact reasons
for the performance you are seeing.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact
[javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.
midrange.com
