Search

Marko Tintor

from San Francisco, CA
Age ~40
Get Report
Connected to:
Jaime T Tintor, 44Mladen Tintor, 40Maria P Tintore, 55John J Tintori, 61Evan Tintorri, 33Hartmut Tintrup, 55Kelly L Tinucci, 58Louis R Tinucci, 73Mark T Tinucci, 39Thomas J Tinus, 70

Marko Tintor Phones & Addresses

  • San Francisco, CA

Resumes

Resumes

Marko Tintor Photo 1

Engineering

View page
Location:
534 4Th St, San Francisco, CA 94107
Industry:
Computer Software
Work:
MemSQL - San Francisco since 2011
Senior Software Engineer
Microsoft 2007 - 2011
Software Design Engineer
Google Inc. - New York 2006 - 2006
Intern Software Engineer
Serbian Object Laboratories - Belgrade, Serbia 2005 - 2005
Intern Software Engineer
Education:
Univerzitet u Beogradu 2003 - 2007
Skills:
Software Development
C++
Software Design
Databases
Marko Tintor Photo 2

Building The Next Generation In-Memory Database Engine

View page
Position:
Senior Software Engineer at MemSQL
Location:
San Francisco, California
Industry:
Computer Software
Work:
MemSQL - San Francisco since 2011
Senior Software Engineer
Microsoft 2007 - 2011
Software Design Engineer
Google Inc. - New York 2006 - 2006
Intern Software Engineer
Serbian Object Laboratories - Belgrade, Serbia 2005 - 2005
Intern Software Engineer
Education:
Univerzitet u Beogradu 2003 - 2007

Publications

Us Patents

Distributed Query Cache In A Database System

View page
US Patent:
20130198231, Aug 1, 2013
Filed:
Jan 30, 2013
Appl. No.:
13/754371
Inventors:
Alex Skidanov - San Francisco CA, US
Marko Tintor - San Francisco CA, US
Nikita Shamgunov - San Francisco CA, US
Assignee:
MemSQL, Inc. - San Francisco CA
International Classification:
G06F 17/30
US Classification:
707770
Abstract:
A distributed query system includes a distributed collection of dynamically created compiled queries. As each client submits a query, a parameterized query skeleton is identified, which identifies the general form of the query, and the parameters associated with the particular query. If a compiled form of the skeletal query is available within the distributed system, it is executed with the parameters of the current query. If the compiled form of the skeletal query is not available within the distributed system, a compiled form is created, and the location of this compiled skeletal query is stored for subsequent access by this client, or other clients. The executable compiled skeletal queries may be stored at each client system, or in a commonly available server storage system.

Reusing Existing Query Plans In A Database System

View page
US Patent:
20130198166, Aug 1, 2013
Filed:
Jan 30, 2013
Appl. No.:
13/754333
Inventors:
Adam PROUT - San Francisco CA, US
Marko Tintor - San Francisco CA, US
Alex Skidanov - San Francisco CA, US
Assignee:
MEMSQL, INC. - San Francisco CA
International Classification:
G06F 17/30
US Classification:
707718
Abstract:
A system and method for executing query plans preprocesses a user's queries to identify and extract select parameters of the query, creates a skeletal query with reference to the extracted parameters, creates and compiles an executable version of the skeletal query, then executes the compiled version of the skeletal query using the particular parameters in the current query. The compiled version of the parameterized skeletal query is stored, and when another query is submitted that matches the skeletal query (but with potentially different parameters), the previously compiled skeleton query is executed with the parameters of this latter query.

Durability Implementation Plan In An In-Memory Database System

View page
US Patent:
20130198139, Aug 1, 2013
Filed:
Jan 30, 2013
Appl. No.:
13/754301
Inventors:
Alex SKIDANOV - San Francisco CA, US
Marko Tintor - San Francisco CA, US
Adam Prout - San Francisco CA, US
Assignee:
MEMSQL, INC. - San Francisco CA
International Classification:
G06F 17/30
US Classification:
707649
Abstract:
A database durability implementation records only committed transactions in a log file. A pair of log files and a pair of snapshot files are maintained. When a snapshot of the database is completed, the ‘current’ log becomes the ‘prior’ log and the other log becomes the ‘current’ log. After the next snapshot is completed, the prior log and prior snapshot may be deleted. Transactions that are not committed are not recorded in the current log, thereby avoiding the need to undo aborted transactions. If a given change is reflected in a completed snapshot, it does not appear in either of the logs; if the change is not yet reflected in a completed snapshot, it is guaranteed to be stored in one of the logs. During recovery, the system assesses both snapshots. The most recent of the completed snapshots is used, and the corresponding log(s) is (are) applied.
Control profile
Marko Tintor from San Francisco, CA, age ~40 Get Report