Source: https://patents.google.com/patent/US9367463B2/en
Timestamp: 2019-08-23 14:17:07
Document Index: 398328472

Matched Legal Cases: ['Application No. 14159175', 'application No. 35215141', 'application No. 35215141', 'application No. 14159175', 'application No. 35215141', 'application No. 35215141']

US9367463B2 - System and method utilizing a shared cache to provide zero copy memory mapped database - Google Patents
System and method utilizing a shared cache to provide zero copy memory mapped database Download PDF
US9367463B2
US9367463B2 US13/827,627 US201313827627A US9367463B2 US 9367463 B2 US9367463 B2 US 9367463B2 US 201313827627 A US201313827627 A US 201313827627A US 9367463 B2 US9367463 B2 US 9367463B2
US13/827,627
US20140281115A1 (en
2013-03-14 Application filed by Palantir Technologies Inc filed Critical Palantir Technologies Inc
2013-03-14 Priority to US13/827,627 priority Critical patent/US9367463B2/en
2013-06-25 Assigned to PALANTIR TECHNOLOGIES, INC. reassignment PALANTIR TECHNOLOGIES, INC. ASSIGNMENT OF ASSIGNORS INTEREST (SEE DOCUMENT FOR DETAILS). Assignors: Biswal, Punya, Ghamsari, Nima, Liu, Beyang, Marinelli, Eugene
2014-09-18 Publication of US20140281115A1 publication Critical patent/US20140281115A1/en
2016-06-14 Publication of US9367463B2 publication Critical patent/US9367463B2/en
Methods and systems for providing a plurality of applications with concurrent access to data are disclosed. One such method includes identifying attributes of an expected data set to be accessed concurrently by the applications, initializing a shared cache with a column data store configured to store the expected data set in columns and creating a memory map for accessing a physical memory location in the shared cache. The method may also include mapping the applications' data access requests to the shared cache with the memory map. Only one instance of the expected data set is stored in memory, so each application is not required to create additional instances of the expected data set in the application's memory address space. Therefore, larger expected data sets may be entirely stored in memory without limiting the number of applications running concurrently.
Embodiments of the invention generally relate to data analysis and, more specifically, to techniques for providing a shared cache as a zero copy memory mapped database.
Some programming languages provide an execution environment that includes memory management services for applications. That is, the execution environment manages application memory usage. The operating system provides each process, including the execution environment, with a dedicated memory address space. The execution environment assigns a memory address space to execute the application. The total addressable memory limits how many processes may execute concurrently and how much memory the operating system may provide to any given process.
In some data analysis systems, applications perform queries against a large common data set, e.g. an application that performs financial analyses on a common investment portfolio. In such a case, the financial analysis application may repeatedly load portions of the entire data set into the application's memory or the application may load the entire expected data set. Frequently, even if multiple applications analyze the same data set, the data is loaded into the memory address space of each application. Doing so takes time and system resources, which increases system latency and effects overall system performance. The amount of memory in a system limits the number of execution environment processes that can run concurrently with memory address space sizable enough to allow the application to load an entire expected data set.
The scalability of the system is limited as the expected data set grows, because the system has to either reduce the number of applications that can run concurrently or increase the rate at which portions of the expected data set must be loaded, causing overall system performance to degrade.
One embodiment of the invention includes a method for a plurality of applications to access a data set concurrently. This method may generally include identifying a plurality of attributes of an expected data set to be accessed concurrently by the plurality of applications and allocating a memory space for a shared cache. The shared cache comprises a column data store configured to store data for each of the plurality of attributes of the expected data set in columns. This method may further include retrieving the expected data set from a database, populating the shared cache with the expected data set; and storing memory address locations corresponding to the columns of the column data store of the shared cache for access by the plurality of applications. Each application generates a memory map from memory locations in a virtual address space of each respective application to the stored address memory locations.
Advantageously, the method stores a single instance of the expected data set in memory, so each application does not need to create an additional instance of the expected data set. Therefore, larger expected data sets may be stored in memory without limiting the number of applications running concurrently.
Further, the method may arrange the expected data set in the shared cache for efficient data analysis. For instance, the method may arrange the expected data set in columns, which facilitates aggregating subsets of the expected data set.
So that the manner in which the features of the present invention recited above can be understood in detail, a more particular description of the invention, briefly summarized above, may be had by reference to embodiments, some of which are illustrated in the appended drawings. It is to be noted, however, that the appended drawings illustrate only typical embodiments of this invention and are therefore not to be considered limiting of its scope, for the invention may admit to other equally effective embodiments.
FIG. 1 is a block diagram illustrating a data analysis system including an application server and configured to implement one or more aspects of the present invention.
FIG. 2 illustrates an example server computing system configured with a shared cache, according to one embodiment.
FIG. 3 is a block diagram of the flow of data in the application server of FIG. 1, according to one embodiment.
FIG. 4 illustrates an example of a shared cache configured as a column store, according to one embodiment.
FIG. 5 illustrates a method for setting up or initializing the shared cache and for providing a memory map to applications, according to one embodiment.
FIG. 6 illustrates a method for accessing a model in the shared cache from the point of view of an application, according to one embodiment.
Embodiments of the invention provide a shared cache as a zero copy memory mapped database. Multiple applications access the shared cache concurrently. In one embodiment, the shared cache is a file that each application maps into the virtual memory address space of that application. Doing so allows multiple applications to access the shared cache simultaneously. Note, in the present context, an expected data set generally refers to records from a database repository designated to be loaded into the shared cache. A process, referred to herein as a synchronizer, populates, and in some cases updates, a data structure storing the expected data set in the shared cache. To access the shared cache, each running application maps the shared cache into a virtual memory address space of the execution environment in which the application runs. The mapping translates virtual memory addresses (in a user address space) to memory addresses in the shared cache (the system address space). In one embodiment, the applications only read data from the data stored in the shared cache. As a result, applications can access the data concurrently without causing conflicts.
In one embodiment, the data structure is a column data store in which data from the database repository is stored contiguously in columns. The applications analyze data entities called models. Models include a combination of data attributes from a database repository and different types of models include different data attributes. The expected data set includes several different types of models. The synchronizer arranges the column data store to include a column for every data attribute of the models included in the expected data set. Application developers build the applications upon data access methods that abstract the interactions with the actual columns of the column data store, so that application developers can readily access the data of a model without regard for the underlying data structure. The columns allow efficient aggregation of the data, because as an application iterates through a data attribute of a group of models, a data access method simply reads sequential entries in a column. For example, an expected data set may include personal checking account models. In such a case, the column data store would include the data of the personal checking account models in columns, such as a column for account balances, a column for account numbers, and a column for recent transactions. The application accesses the columns of data through calls to data access methods.
FIG. 1 is a block diagram illustrating an example data analysis system 100, according to one embodiment. As shown, the data analysis system 100 includes a client computing system 105, a client 110, a server computer system 115, an application server 120, and a database repository 115. The client 110 runs on the client computing system 105 and requests data analysis activities from the application server 120 that performs the data analysis activities at a server computing system 115 on data retrieved from the database repository 150.
The client 110 translates user inputs into requests for data analysis by the application server 120. The client 110 runs on computing systems connected to the server computing system 115 over a network. For example, the client 110 may be dynamic web pages in a browser or a web-based Java® application running on a client computing system 105. Alternatively, the client 110 may run on the same server computing system 115 as the application server 120. In any event, a user interacts with the data analysis system 100 through client 110.
The application server 120 performs the analysis upon data read from the database repository 150. A network connects the database repository 150 and the server computing system 115. The database repository 150 stores records of data. For example, the database repository 150 may be a Relational Database Management System (RDBMS) storing data as rows in relational tables. Alternatively, the database repository 150 may exist on the same server computing system 115 as the application server 120.
In one embodiment, a user sets up an application server 120 with an expected data set. Once configured, the expected data set is made available to multiple clients 110 for analysis.
FIG. 2 illustrates an example server computing system 115 configured with a shared cache 228, according to one embodiment. The shared cache 228 provides applications 222 running in execution environments 221 with concurrent access to data stored in the shared cache 228. As shown, the server computing system 115 includes, without limitation, a central processing unit (CPU) 250, a network interface 270, a memory 220, and a storage 230, each connected to an interconnect (bus) 240. The server computing system 115 may also include an I/O device interface 260 connecting I/O devices 280 (e.g., keyboard, display and mouse devices) to the computing system 115. Further, in context of this disclosure, the computing elements shown in server computing system 115 may correspond to a physical computing system (e.g., a system in a data center) or may be a virtual computing instance executing within a computing cloud.
The CPU 250 retrieves and executes programming instructions stored in memory 220 as well as stores and retrieves application data residing in memory 220. The bus 240 is used to transmit programming instructions and application data between the CPU 250, I/O device interface 260, storage 230, network interface 270, and memory 220. Note, CPU 250 is included to be representative of a single CPU, multiple CPUs, a single CPU having multiple processing cores, a CPU with an associate memory management unit, and the like. The memory 220 is generally included to be representative of a random access memory. The storage 230 may be a disk drive storage device. Although shown as a single unit, the storage 230 may be a combination of fixed and/or removable storage devices, such as fixed disc drives, removable memory cards, or optical storage, network attached storage (NAS), or a storage area-network (SAN).
The requests for data analyses and the results of data analyses are transmitted between the client 110 and the applications 222 over the network via the network interface 270. Illustratively, the memory 220 includes applications 222 running in execution environments 221, a synchronizer 225, and a shared cache 228. The applications 222 perform data analyses using data from the shared cache 228. Prior to performing a data analysis, the synchronizer 225 initializes the shared cache 228 with data retrieved from the database repository 150. For example, the synchronizer 225 may issue database queries over the network to the database repository 150 via the network interface 270. Once the synchronizer 225 initializes (or updates) the shared cache 228, an application 222 maps the shared cache 228 into the virtual address space local to the execution environment 221 of the application 222. This memory mapping allows the application 222 to access the shared cache 228 and read the data from the shared cache 228. When other applications 222 also map the shared cache into the virtual address space local to the execution environment 221 of the applications 222, then the applications 222 may concurrently access the shared cache 228.
Although shown in memory 220, the shared cache 228 may be stored in memory 220, storage 230, or split between memory 220 and storage 230. Further, although shown as a single element the shared cache 228 may be divided or duplicated.
In some embodiments, the database repository 150 may be located in the storage 230. In such a case, the database queries and subsequent responses are transmitted over the bus 240. As described, the client 110 may also be located on the server computing system 115, in which case the client 110 would also be stored in memory 220 and the user would utilize the I/O devices 280 to interact with the client 110 through the I/O device interface 260.
FIG. 3 illustrates a flow of data as multiple applications 222 concurrently access the shared cache 228 on the application server 120, according to one embodiment. As shown, the application server 120 includes the synchronizer 225, shared cache 228, and applications 222 running in execution environments 221, and a memory map 315 for each execution environment 221. Further, each application 222 accesses one or more models 310.
The application 222 (application 222(0), for example), analyzes models 310 that include a combination of data attributes from the database repository 150. To setup the shared cache 228 for the applications 222, the synchronizer 225 reads data from the database repository 150. The synchronizer 225 writes data to the shared cache 228. As it writes the data to the shared cache 228, the synchronizer 225 organizes the data according to a data structure. For example, the synchronizer may organize the data into a column data store for efficient data access. The synchronizer 225 provides address references to the shared cache 228 that the applications 222 use for accessing the data of the models 310 in the data structure of the shared cache 228.
In one embodiment, the operating system of the server computing system 115 manages the memory map 315 to the shared cache 228. The memory map 315 maps a virtual address space local to each execution environment 221 to physical memory addresses in the shared cache 228. The address space of each execution environment 221 is a range of virtual memory locations. The virtual memory locations appear to the execution environment 221 as one large block of contiguous memory addresses. The memory map 315 contains a table of virtual memory locations and corresponding physical memory locations. The virtual memory locations are mapped to the physical memory locations in either memory 220 or storage 230 by looking up the virtual memory location in the memory map 315 and retrieving the corresponding physical memory location. When an application reads data from the virtual address space, a memory map 315 translates a memory address from the virtual address space to the physical address space. Specifically, the application receives the data from the physical memory location in the address space of the shared cache 228.
The application 222, the execution environment 221, the operating system, or any other component responsible for translating memory addresses may create this mapping. For example, an application 222 may be a Java® application running in the Java® Virtual Machine (JVM) execution environment. In such a case, the operating system provides the JVM virtual memory address space to execute the Java® application for data analysis. The JVM runs the Java® application in a portion of the virtual memory address space, called the heap. Once created, the memory map 315 maps a portion of the remaining virtual memory address locations to physical memory locations in the address space of the shared cache 228. When multiple JVMs run Java® applications for data analysis on the same application server 120, the memory maps 315 all map to the same shared cache 228, providing concurrent access.
FIG. 4 illustrates an example of the shared cache 228 configured as a column data store 410, according to one embodiment of the present invention. As shown, the shared cache 228 includes the column data store 410, which includes columns 440. An application 222 accesses the data of a model 310 from the columns 440 that correspond to the attributes of the model 310. An analysis based upon aggregating a particular attribute of many models 310 of the same type may access a particular column 440(0) that corresponds to the attribute instead of all columns 440 that correspond to that type of model 310. Note, the synchronizer 225 may arrange the columns 440 for a particular type of model 310 together or according to a number of different designs.
In one embodiment, a user configures the data analysis system 100 for analyzing data of a given domain by selecting types of models 310 to analyze. The models 310 include data attributes from the database repository 150, so the synchronizer 225 retrieves the database records to populate the column data store 410 based upon the selected models 310. The synchronizer 225 creates the column data store 410 to include a column 440 for each attribute of the selected models 310.
For example, assume a model 310 representing a home mortgage is composed of three attributes, such as the bank name, loan amount, and the mortgage issue date. In such a case, the synchronizer 225 would query the database repository 150 for the data to build three columns 440 in the column data store 410. The first column 440(0) would include a list of bank names, the second column 440(1) would include the loan amounts, and the last column 440(C−1) would include the mortgage issue date. Depending on the organization of the database repository 150, a model 310 may include data from a single record in a table in the database repository 150, data from multiple tables in the database repository 150, or aggregated data from multiple records in the database repository 150.
An application 222 accesses the data of a model 310 by reading the data values at equal indexes across the columns 440 of the model. Alternatively, the application may iterate through one attribute of a group of models, which involves reading sequential entries in a single column 440.
In the example of a model 310 representing a home mortgage, the application 222 may call a data access method to create an aggregate of an attribute of the model 310, such as the loan amounts attribute. The data access method would read sequential entries in the second column 440(1) that includes the loan amounts. The data access method only needs to find, read, and aggregate the entries in the one column 440(1). This is very efficient because the application 222 easily calculates the memory addresses of sequential entries by simply incrementing a pointer from one entry to the next.
A database repository 150 organizes data by records in tables, so to generate the same average loan amount value, without using the shared cache 228 and the column data store 410, a table with the loan amount attribute would need to be located and the records from the table would need to be read to find the loan amount data. To find the loan amount data in a record the data analysis system would have to access the entire record and then the data analysis system would have to follow pointers from one data item of the record to the next data item of the record until finding the loan amount value of the record.
The contiguous storage of the data values in columns 440 in a column data store 410 supports data aggregation. As a result, an application 222 only needs to read the columns 440 involved in an analysis, instead of entire records; as previously discussed in the example of determining the average home mortgage loan amount. Not only does less data have to be read, but reading the relevant data is more efficient because the relevant data is stored sequentially in memory 220, so it is easy to determine the address of subsequent entries as the application 222 iterates through the column 440. Further, since the data entries are stored contiguously, the data spans fewer pages of memory 220, reducing the overhead associated with swapping memory pages.
As described the synchronizer 225 provides address reference to a column 440 to the application 222 for accessing data in the column 440. The address reference is a virtual memory location. The operating system maps the virtual memory location of the column 440 in the virtual memory address space in which an application 222 runs to the physical memory location of the column 440 in a shared cache 228. Therefore, the application 222 accesses the column 440 as though the column 440 was included in one large block of contiguous memory addresses belonging to the execution environment 221 that the application 222 runs in.
FIG. 5 illustrates a method for initializing the shared cache 228 and providing the memory map 315 to the applications 222, according to one embodiment. Note, in this example, the initialization of the shared cache 228 is discussed from the perspective of the synchronizer 225. Although the method steps are described in conjunction with the systems of FIGS. 1-4, persons of ordinary skill in the art will understand that any system configuration to perform the method steps, in any order, is within the scope of the invention.
As shown, method 500 begins at step 505, where the synchronizer 225 receives a list of models 310 to include in the expected data set. A user defines the expected data set available for analysis by selecting which models 310 the system should make available for multiple applications 222 to analyze concurrently. The user may make the selections from a user interface at the application server 120, or may create a script that includes the selections.
In step 510, the synchronizer 225 creates a shared cache 228 as a file in memory 220. One skilled in the art will appreciate that the shared cache 228 could be stored in memory 220 only or in some combination of memory 220 and storage 230. The operating system generally determines the physical location of the shared cache 228 or portions of the shared cache 228 based upon the amount of memory 220 available. The server computer system 115 contains sufficient memory 220 to store the entire shared cache 228 in memory 220.
In step 515, the synchronizer 225 initializes a column data store 410 in the shared cache 228 by initializing columns 440 for the attributes defined by the selected models 310. The synchronizer 255 creates pointers to memory locations in the shared cache 228 for each column 440.
In step 520, the synchronizer 225 retrieves the records included in the expected data set from the database repository 150. The synchronizer 225 retrieves the records by querying the database repository 150. For example, the database repository 150 may be a structured query language (SQL) based RDBMS, where the synchronizer 225 issues SQL queries as defined by the selected data types to retrieve records from the tables of the database repository 150.
In step 525, the synchronizer 225 stores data values from the retrieved records as contiguous entries in the appropriate columns 440. The columns 440 correspond to the attributes of the models 310. As the synchronizer 225 processes each retrieved record, the synchronizer 225 copies the individual data values into the appropriate column 440. The synchronizer 225 stores the first entry of a column 440 at the memory location of the pointer that the synchronizer 225 created for the column 440 in step 515. The data values from the first retrieved record become the first entries in the columns 440, the data values from the second retrieved record become the second entries in the columns 440, and so on. Thus, each data record that the synchronizer 225 retrieves is stored as multiple entries at the same index location in multiple columns 440.
In step 530, the synchronizer 225 provides address references of the columns 440 in the shared cache 228 to the applications 222. The address references may be the locations of the first entries of the columns 440 in the shared cache 228. The address references may be stored in a file that each application 222 is able to access.
Although the synchronizer creates the columns 440 in the shared cache 228, the address references provided to a model 310 may be virtual address locations. The model 310 may be used by an application 222 running in an execution environment 221 with a local address space of virtual memory. A memory map 315 translates the virtual address locations to physical memory locations in the columns 440 in the shared cache 228. The creation of the column data store 410 in the shared cache 228 that is outside of the virtual memory space of a single execution environment 221 allows the synchronizer 225 to provide address references to an interface 310 used by multiple applications 222 in multiple execution environments 221. Therefore, multiple applications can use models 310, which have the virtual address locations mapped to the shared cache 228, to access the same data in the columns 440 concurrently.
In some embodiments of this invention, the operating system of the server computing system 115 or the program execution environment creates and maintains the memory map 315 of the shared cache 228. In such a case, the memory map 315 contains physical memory locations of the shared cache 228, but not necessarily the locations of the columns 440 in the shared cache 228. A synchronizer 225 would provide virtual address locations to an application 222 that represent offsets into the shared cache 228 for the physical memory location of the columns 440.
FIG. 6 illustrates a method for accessing a model 310 in the shared cache 228 from the point of view of the application 222, according to one embodiment. Although the method steps are described in conjunction with the systems of FIGS. 1-4, persons of ordinary skill in the art will understand that any system configuration to perform the method steps, in any order, is within the scope of the invention.
As shown, method 600 begins at step 605, where the application 222 creates a memory map 315 of the shared cache 228. As discussed above, the memory map 315 identifies virtual memory locations and corresponding physical memory locations in the shared cache 228. The shared cache 228 is a memory mapped file, which the application 222 first opens and then maps into the execution environment's 221 memory. For example, assuming the application 222 is a Java® application, the application 222 opens the shared cache 228 file as a RandomAccessFile. Then the application 222 creates a MappedByteBuffer, which maps to the shared cache 228. Once the application 222 creates a MappedByteBuffer, the application 222 is able to read bytes of data from specific locations in the MappedByteBuffer that are mapped to locations in the shared cache 228. The application utilizes models 310 to read the data from the data structure in the shared cache 228.
In step 610, the application 222 makes a data access method call to retrieve the data of a model 310. Depending on how the data access method has been developed, the data access method may retrieve a subset of the raw data stored in the shared cache 228 or the data access method may retrieve an aggregate of the data stored in the shared cache 228.
In step 615, the interface 310 requests data from address references in the memory mapped representation of the shared cache 228. According to one embodiment of the invention, the address references are locations of the first entries in the columns 440 of the column data store 410. The interface 310 may request data beginning at the first entry of the column 440 or may calculate an offset location. If the application 222 is a Java® application, the requested memory locations are virtual memory locations in the MappedByteBuffer. As noted, the MappedBytebuffer is the memory mapped representation of the shared cache 228, so the MappedBytebuffer is included in the virtual address space of the execution environment 221 that the application 222 runs in.
In step 620, the operating system maps the virtual memory locations from the virtual address space of the execution environment 221 to the physical memory locations in the shared cache 228. According to one embodiment, the operating system identifies the virtual memory locations in a table in the memory map 315 and retrieves the corresponding physical memory locations.
In step 625, the application 222 receives the requested data from the shared cache 228. According to one embodiment of the invention, the operating system performs the memory mapping, so the application 222 receives the requested data as if the data had been requested from the address space of the execution environment 221.
In step 630, the application 222 processes the retrieved data according to the intended function of the data analysis application. For example, the application 222 may report some aggregate or subset of the requested data in the shared cache 228 to the client 110 or may issue additional data requests based upon the already retrieved data. This processing may occur as part of the data access method call or after the data access method call has returned.
1. A method for providing a plurality of applications with concurrent access to an expected data set from a database repository, the method comprising:
receiving a list of models to include in the expected data set for multiple applications to analyze concurrently, the models including a combination of data attributes from the database repository, wherein the expected data set includes different types of models and different types of models include different data attributes;
identifying in the database repository, a portion of the database repository comprising a plurality of data attributes of the expected data set to be accessed concurrently by the plurality of applications;
allocating a memory space for a shared cache, wherein the shared cache comprises a column data store configured to store data for each of the plurality of attributes of the expected data set in columns;
retrieving the expected data set from a database;
populating the shared cache with the expected data set; and
storing memory address locations corresponding to the columns of the column data store of the shared cache for access by the plurality of applications, wherein each application generates a memory map which maps memory locations in a virtual address space of the respective application to the stored memory address locations.
2. The method of claim 1, wherein each of the plurality of applications accesses the data set by:
requesting data from one or more of the memory locations in the virtual address space allocated to the application;
mapping memory locations in the virtual address space to corresponding memory address locations of the shared cache, via the memory map; and
accessing the requested data from the mapped memory locations in the shared cache.
3. The method of claim 1, wherein storing the data of each of the plurality of attributes of the expected data set in columns, comprises:
dividing one or more data records retrieved from the database into a plurality of attribute values;
identifying a contiguous memory location in the shared cache for each attribute value; and
storing each attribute value in one of the identified contiguous memory locations.
4. The method of claim 1, wherein a plurality of object-oriented representations of the expected data set are provided to the plurality of applications by:
initializing a plurality of objects with data access methods;
storing the memory address locations corresponding to the columns of the column data store of the shared cache in the objects; and
providing the plurality of objects for access by the plurality of applications.
5. The method of claim 4, wherein at least one of the plurality of applications access the data set by:
calling a data access method of one of the objects; and
receiving the requested data from the data access method of the object.
6. The method of claim 1, wherein the shared cache is configured to provide read only access to the plurality of applications.
7. The method of claim 1, wherein the shared cache is updated by:
identifying a plurality of attributes of an updated expected data set;
re-allocating the memory space for the shared cache;
retrieving an updated expected data set from the database;
populating the shared cache with the updated expected data set; and
storing updated memory address locations corresponding to the columns of the column data store in the shared cache.
8. A non-transitory computer-readable storage medium storing instructions that, when executed by a processor, cause the processor to perform an operation for providing a plurality of applications with concurrent access to an expected data set from a database repository, the operation comprising:
9. The non-transitory computer-readable storage medium of claim 8, wherein each of the plurality of applications accesses the data set by:
10. The non-transitory computer-readable storage medium of claim 8, wherein storing the data of each of the plurality of attributes of the expected data set in columns, comprises:
11. The non-transitory computer-readable storage medium of claim 8, wherein a plurality of object-oriented representations of the expected data set are provided to the plurality of applications by:
12. The non-transitory computer-readable storage medium of claim 11, wherein at least one of the plurality of applications access the data set by:
13. The non-transitory computer-readable storage medium of claim 8, wherein the shared cache is configured to provide read only access to the plurality of applications.
14. The non-transitory computer-readable storage medium of claim 8, wherein the shared cache is updated by:
a memory storing one or more programs; and
a processor configured to execute the one or more programs to perform an operation for providing a plurality of applications with concurrent access to data, the operation comprising:
16. The system of claim 15, wherein each of the plurality of applications accesses the data set by:
17. The system of claim 15, wherein storing the data of each of the plurality of attributes of the expected data set in columns, comprises:
18. The system of claim 15, wherein a plurality of object-oriented representations of the expected data set are provided to the plurality of applications by:
19. The system of claim 18, wherein at least one of the plurality of applications access the data set by:
20. The system of claim 15, wherein the shared cache is configured to provide read only access to the plurality of applications.
21. The system of claim 15, wherein the shared cache is updated by:
US13/827,627 2013-03-14 2013-03-14 System and method utilizing a shared cache to provide zero copy memory mapped database Active 2033-12-22 US9367463B2 (en)
US13/827,627 US9367463B2 (en) 2013-03-14 2013-03-14 System and method utilizing a shared cache to provide zero copy memory mapped database
EP20140159175 EP2778972A1 (en) 2013-03-14 2014-03-12 Shared cache used to provide zero copy memory mapped database
CA2846417A CA2846417C (en) 2013-03-14 2014-03-13 Shared cache used to provide zero copy memory mapped database
AU2014201593A AU2014201593C1 (en) 2013-03-14 2014-03-14 Shared cache used to provide zero copy memory mapped database
NZ62248514A NZ622485A (en) 2013-03-14 2014-03-14 Shared cache used to provide zero copy memory mapped database
US15/173,526 US9652291B2 (en) 2013-03-14 2016-06-03 System and method utilizing a shared cache to provide zero copy memory mapped database
US15/173,526 Continuation US9652291B2 (en) 2013-03-14 2016-06-03 System and method utilizing a shared cache to provide zero copy memory mapped database
US20140281115A1 US20140281115A1 (en) 2014-09-18
US9367463B2 true US9367463B2 (en) 2016-06-14
ID=50280162
US13/827,627 Active 2033-12-22 US9367463B2 (en) 2013-03-14 2013-03-14 System and method utilizing a shared cache to provide zero copy memory mapped database
US15/173,526 Active US9652291B2 (en) 2013-03-14 2016-06-03 System and method utilizing a shared cache to provide zero copy memory mapped database
US (2) US9367463B2 (en)
EP (1) EP2778972A1 (en)
AU (1) AU2014201593C1 (en)
CA (1) CA2846417C (en)
NZ (1) NZ622485A (en)
US9652291B2 (en) * 2013-03-14 2017-05-16 Palantir Technologies, Inc. System and method utilizing a shared cache to provide zero copy memory mapped database
2013-03-14 US US13/827,627 patent/US9367463B2/en active Active
2014-03-12 EP EP20140159175 patent/EP2778972A1/en active Pending
2014-03-13 CA CA2846417A patent/CA2846417C/en active Active
2014-03-14 AU AU2014201593A patent/AU2014201593C1/en active Active
2014-03-14 NZ NZ62248514A patent/NZ622485A/en unknown
2016-06-03 US US15/173,526 patent/US9652291B2/en active Active
Claims in European Application No. 14159175.0-1951, dated Jul. 2014, 2 pages.
Current Claims in New Zealand application No. 35215141/AJS, dated Apr. 2014, 5 pages.
Current Claims in New Zealand application No. 35215141/AJS, dated Jun. 2014, 5 pages.
European Patent Office, "Search Report" in application No. 14159175.0-1951, dated Jul. 17, 2014, 10 pages.
Intellectual Property Office New Zealand, "First Examination Report" in application No. 35215141/AJS, dated Apr. 1, 2014, 2 pages.
Intellectual Property Office New Zealand, "Further Examination Report" in application No. 35215141/AJS, dated Jun. 13, 2014, 2 pages.
Ivanova et al., "An Architecture for Recycling Intermediates in a Column-Store", SIGMOD, dated Jul. 2009, 12 pages.
AU2014201593A1 (en) 2014-10-02
EP2778972A1 (en) 2014-09-17
US9652291B2 (en) 2017-05-16
AU2014201593B2 (en) 2018-02-22
US20160283277A1 (en) 2016-09-29
NZ622485A (en) 2014-11-28
US20140281115A1 (en) 2014-09-18
CA2846417A1 (en) 2014-09-14
AU2014201593C1 (en) 2018-06-14
CA2846417C (en) 2018-08-14
US7024420B2 (en) 2006-04-04 Run-time access techniques for database images
Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:BISWAL, PUNYA;LIU, BEYANG;MARINELLI, EUGENE;AND OTHERS;SIGNING DATES FROM 20130519 TO 20130624;REEL/FRAME:030684/0722