US 12,455,856 B2
Single namespace for high performance computing system
William Patrick Baird, Orinda, CA (US); Mikhail Zhagrov, San Francisco, CA (US); Alexander David Younts, West Lafayette, IN (US); Varsha Kohirkar, Palo Alto, CA (US); and Kumud Kalia, Redwood City, CA (US)
Assigned to Guardant Health, Inc., Palo Alto, CA (US)
Filed by GUARDANT HEALTH, INC., Palo Alto, CA (US)
Filed on Apr. 1, 2025, as Appl. No. 19/097,019.
Application 19/097,019 is a continuation of application No. 18/926,954, filed on Oct. 25, 2024, granted, now 12,287,759.
Claims priority of provisional application 63/656,184, filed on Jun. 5, 2024.
Claims priority of provisional application 63/627,636, filed on Jan. 31, 2024.
Claims priority of provisional application 63/593,354, filed on Oct. 26, 2023.
Prior Publication US 2025/0258795 A1, Aug. 14, 2025
This patent is subject to a terminal disclaimer.
Int. Cl. G06F 17/30 (2006.01); G06F 16/14 (2019.01); G06F 16/18 (2019.01)
CPC G06F 16/148 (2019.01) [G06F 16/1873 (2019.01)] 20 Claims
OG exemplary drawing
 
1. A method comprising:
obtaining, by a computing system including memory and one or more processors, a request to write to file data from a user of the computing system, wherein the file data includes a number of objects stored in a primary data store, the file data is represented in a local file system as a file, and the computing system is at least one of maintained, controlled, or administered by a first entity and the primary data store is at least one of maintained, controlled, or administered by a second entity that includes a cloud storage service provider;
accessing, by the computing system and using the local file system, metadata corresponding to the file data, wherein the metadata indicates a data object of the primary data store that includes the file data;
causing, by the computing system, the file data to be stored in a temporary data store of the first entity, wherein the temporary data store is accessible to the local file system;
causing, by the computing system, a locking object to be generated in the file data and stored in the primary data store, the locking object indicating an identifier of the user and indicating a lock status that additional users of the computing system are unable to modify the file data;
causing, by the computing system and based on the request to write to the file data, one or more computational operations to be performed with respect to the file data to produce a modified version of the file data, and store the modified version of the file data in the temporary data store;
in response to determining that the one or more computational operations corresponding to the request to write to the file data have completed, causing, by the computing system, at least one of (i) the locking object to be removed from the file data or (ii) modifying the lock status to indicate that the file data is modifiable by one or more additional users of the computing system; and
causing, by the computing system, the modified version of the file data to be stored in the data object of the primary data store via the local file system, and removed from the temporary data store;
wherein causing the modified version of the file data to be removed from the temporary data store is part of a process to dehydrate data related to the file data in the temporary data store, the process including storing updated metadata of the file data stored by the local file system, and producing a stub file during the dehydration process, wherein the stub file indicates at least one of an identifier of the file data or a storage location of the file data in the primary data store.