Abstract: A new approach is proposed that contemplates systems and methods to support file synchronization between a local host and a cloud storage via one or more local content appliances (CAs), wherein each content appliance is a storage device/host configured to locally maintain documents and files previously downloaded from the cloud storage. First, a client agent at the local host discovers and connects to the CA that manage its files locally. To access a file/document that is not cached on its local host, the client agent requests and receives the file from the CA instead of downloading it directly from the cloud storage. When parts of the file are updated locally by the client, the client agent is configured to transmit the updated file to the CA, wherein the updated file is considered as having been fully committed from the client's perspective. The CA then synchronizes with and uploads the revised file to the cloud storage and/or other CAs in the background.

Abstract: A new approach is proposed that contemplates systems and methods to support performance tuning of software running on a host/computing device. Specifically, a performance tuner is assigned to and associated with each background process running on the host, wherein the performance tuner is configured to monitor system resource usage by the background process in real time via a plurality of handlers deployed to a plurality of types of system resources of the host. Here, the system resources include but are not limited to CPU, memory/storage, and bandwidth of the network connections of the host. If the system resource usage by the background process is too high (e.g., causing performance degradation of foreground processes viewed/used by a user of the host), the performance tuner is configured to dynamically dispatch the background process—slow it down to scale back its system resource usage.

Abstract: A new approach is proposed that contemplates systems and methods to support offline file system synchronization and sharing with cloud storage via a virtual file system (VFS) configured to provide a complete view of all file files/file folders in a user's account. The VFS separates the storage of the files and their metadata into two primary databases—a staging database where local changes to the files are stored and a file database, which is a cloud-synchronized copy of path structure and metadata information of the files and file folders. The VFS first pulls/retrieves the latest version of a file to be modified from the cloud based on metadata in the file DB and updates the locally-stored version of the file based on the version retrieved from the cloud. Once the file is modified by the user locally via a client (even when the client is offline), the VFS commits and consolidates all the changes made by this and possibly other users to the file in the staging DB before synchronizing the changes to the cloud.

Abstract: A new approach is proposed that contemplates systems and methods to support file synchronization between a local host and a cloud storage via one or more local content appliances (CAs), wherein each content appliance is a storage device/host configured to locally maintain documents and files previously downloaded from the cloud storage. First, a client agent at the local host discovers and connects to the CA that manage its files locally. To access a file/document that is not cached on its local host, the client agent requests and receives the file from the CA instead of downloading it directly from the cloud storage. When parts of the file are updated locally by the client, the client agent is configured to transmit the updated file to the CA, wherein the updated file is considered as having been fully committed from the client's perspective. The CA then synchronizes with and uploads the revised file to the cloud storage and/or other CAs in the background.

Abstract: A cloud file event server transmits file events necessary to synchronize a file system of a file share client. A tree queue director circuit receives file events and stores each one into a tree data structure which represents the hierarchical paths of files within the file share client. An event normalization circuit sorts the file events stored at each node into sequential order and moots file events which do not have to be performed because a later file event makes them inconsequential. A thread scheduling circuit assigns a resource to perform file events at a first node in a hierarchical path before assigning one or more resources to a second node which is a child of the first node until interrupted by the tree queue director circuit or until all file events in the tree data structure have been performed.

Abstract: A cloud file event server transmits file events necessary to synchronize a file system of a file share client. A tree queue director circuit receives file events and stores each one into a tree data structure which represents the hierarchical paths of files within the file share client. An event normalization circuit sorts the file events stored at each node into sequential order and moots file events which do not have to be performed because a later file event makes them inconsequential. A thread scheduling circuit assigns a resource to perform file events at a first node in a hierarchical path before assigning one or more resources to a second node which is a child of the first node until interrupted by the tree queue director circuit or until all file events in the tree data structure have been performed.