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 call the execution path drops into the kernel - and then if required - an inter-process call to the mmfsd daemon process. From: Skylar Thompson <[email protected]> To: [email protected] Date: 11/30/2017 01:42 PM Subject: Re: [gpfsug-discuss] FIle system vs Database Sent by: [email protected] 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 application... > > Regardless of file system, `ls -1 | grep ...` in a huge directory is not > going to be a good idea. But stats and/or opens on a huge directory to > look for a particular file should work pretty well... I've wondered if it would be worthwhile having POSIX look-alike commands like ls and find that plug into the GPFS API rather than making VFS calls. That's of course a project for my Copious Free Time... -- -- Skylar Thompson ([email protected])
_______________________________________________ gpfsug-discuss mailing list gpfsug-discuss at spectrumscale.org http://gpfsug.org/mailman/listinfo/gpfsug-discuss
