Abstract: The present disclosure relates, according to some embodiments, to subsea fluid storage systems that may automatically and/or continuously compensate for subsea pressure changes. A subsea fluid storage unit with passive pressure compensation may comprise a vessel and a deformable bladder disposed within the vessel. A vessel may comprise a top port, a bottom port, and an internal vessel volume. A deformable bladder may comprise a first end and a second end. A second end may comprise a bladder opening that may be fluidically connected to a top port or a bottom port of a vessel. A deformable bladder may define an internal bladder volume that may be suitable for storage of fluids and/or chemicals.

Abstract: The present disclosure relates, according to some embodiments, to subsea fluid storage systems that may automatically and/or continuously compensate for subsea pressure changes. A subsea fluid storage unit with passive pressure compensation may comprise a vessel and a deformable bladder disposed within the vessel. A vessel may comprise a top port, a bottom port, and an internal vessel volume. A deformable bladder may comprise a first end and a second end. A second end may comprise a bladder opening that may be fluidically connected to a top port or a bottom port of a vessel. A deformable bladder may define an internal bladder volume that may be suitable for storage of fluids and/or chemicals.

Abstract: A technique involves placing a data acceleration engine between an end user device and a host device. The host device provides data associated with a client application to the data acceleration engine, which provides the data to the end user device. If the data acceleration engine is on the host device, content from a datastore is served to the data acceleration engine as if the data acceleration engine were a client running the client application locally; therefore, latency normally associated with a network between the content datastore and the client device is eliminated. If the data acceleration engine is on the end user device and has received at least some data in advance of a relevant query, responses to the query also do not have latency associated with a network. The data acceleration engine can be implemented as a series of data acceleration engines between end user and host devices.

Abstract: A technique involves placing a data acceleration engine between an end user device and a host device. The host device provides data associated with a client application to the data acceleration engine, which provides the data to the end user device. If the data acceleration engine is on the host device, content from a datastore is served to the data acceleration engine as if the data acceleration engine were a client running the client application locally; therefore, latency normally associated with a network between the content datastore and the client device is eliminated. If the data acceleration engine is on the end user device and has received at least some data in advance of a relevant query, responses to the query also do not have latency associated with a network. The data acceleration engine can be implemented as a series of data acceleration engines between end user and host devices.