Hello,
This is an announcement for the event held just before SCA18 and general call
out for user use cases or presentations that you would like to present, at the
inaugural Spectrum Scale Usergroup Singapore on the Monday 26th March 2018,
Sentosa, Singapore.
This is being held in conjunction
Indeed, for a very large directory you might get some speedup using
samples/ilm/mmfind directory -ls -maxdepth 1
There are some caveats, the same as those for the command upon which
mmfind rests, mmapplypolicy.
From: Skylar Thompson
To:
On 30/11/17 18:01, Skylar Thompson wrote:
[SNIP]
To be fair, a lot of our biomedical/informatics folks have no choice in the
matter because the vendors are imposing a filesystem-as-a-database paradigm
on them. Each of our Illumina sequencers, for instance, generates a few
million files per
Generally the GPFS API will give you access to some information and
functionality that are not available via the Posix API.
But I don't think you'll find significant performance difference in cases
where there is functional overlap.
Going either way (Posix or GPFS-specific) - for each API
On Thu, Nov 30, 2017 at 01:34:05PM -0500, Marc A Kaplan wrote:
> It would be interesting to know how well Spectrum Scale large directory
> and small file features work in these sort of DB-ish applications.
>
> You might want to optimize by creating a file system provisioned and tuned
> for such
It’s my understanding and experience that all member nodes of two clusters that
are multi-clustered must be able to (and will eventually given enough
time/activity) make connections to any and all nodes in both clusters. Even if
you don’t designate the 2 protocol nodes as contact nodes I would
Um no, you are talking GPFS protocol between cluster nodes still in
multicluster. Contact nodes are where the remote cluster goes to start with,
but after that it's just normal node to node gpfs traffic (not just the contact
nodes).
At least that is my understanding.
If you want traffic
On Wed, 2017-11-29 at 12:08 -0700, Nikhil Khandelwal wrote:
[SNIP]
> Since file systems created at 4.X.X and earlier used a block size
> that kept this allocation in mind, there should be very little impact
> on existing file systems.
That is quite a presumption. I would say that file systems
Oh? I specifically remember Sven talking about the >32 subblocks on the context
of file creation speed in addition to space efficiency. If what you’re saying
is true, then why do those charts show that feature in the context of file
creation performance and specifically mention it as a