MétaCan
Menu
Back to cohort
Record W2618037119 · doi:10.1145/3019612.3019870

Next generation JDBC database drivers for performance, transparent caching, load balancing, and scale-out

2017· article· en· W2618037119 on OpenAlexaff
Ramon Lawrence, Erik Brandsberg, Roland Lee

Bibliographic record

Venuenot available
Typearticle
Languageen
FieldComputer Science
TopicCloud Computing and Resource Management
Canadian institutionsUniversity of British Columbia, Okanagan CampusUniversity of British Columbia
Fundersnot available
KeywordsComputer scienceNoSQLDatabaseCloud databaseDatabase tuningCacheFlexibility (engineering)ExploitCloud computingDatabase testingDistributed databaseViewDatabase designScalabilityOperating systemComputer security

Abstract

fetched live from OpenAlex

Despite having a significant impact on overall data system performance, database drivers connecting the application to the database system have not innovated at the same pace as the database systems themselves. This work describes a database driver designed for the requirements of cloud-based systems requiring flexibility, high availability, scaling, and performance. The unique contribution is a rule-based query routing system that supports real-time configurations and optimizations without requiring any changes to the application code or database system. With the increasing migration of applications and databases to the cloud as well as different database technologies such as NoSQL systems, this flexibility allows application owners to optimize and migrate legacy applications to exploit the advantages of new database technologies. Experimental results demonstrate how queries cached by the driver can improve query response times by an order of magnitude and reduce the overall load on the database system by up to 50+.

Fetched live from OpenAlex and de-inverted. Abstracts are not stored in this database: the inverted indexes are 8.6 GB of the frame’s 9.3 GB of text, and the host has 13 GB free.

How this classification was reachedexpand

Full frame machine prediction

Teacher imitation

Not calibrated prevalence, not ground truth. Human validation pending. The Gemma side is a direct model label for every work in the frame, read from the title-only record. The Codex side is a classifier learned from the 10,348 direct Codex labels and calibrated to design-weighted sample rates; fields without enough sample support carry no Codex call. Candidate is the union of the two sides; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels.

metaresearch head score (Codex)0.004
metaresearch head score (Gemma)0.008
Version: metacan-v3-hybrid-931329e0061cValidation status: machine_predicted_unvalidated
Candidate categoriesnone
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Not applicable · Consensus signal: none
GenreCandidate signal: Methods · Consensus signal: Methods
Teacher disagreement score0.012
Threshold uncertainty score0.023

Distilled classifier scores by category (both heads)

CategoryCodexGemma
Metaresearch0.0040.008
Meta-epidemiology (narrow)0.0010.001
Meta-epidemiology (broad)0.0010.001
Bibliometrics0.0010.001
Science and technology studies0.0010.001
Scholarly communication0.0050.004
Open science0.0040.002
Research integrity0.0010.003
Insufficient payload (model declined to judge)0.0060.004

Machine scores (provisional)

The two teacher heads of the student model, read on this work. A score orders the frame for review; it never asserts a category, and the validation status ships verbatim with every row.

Baseline scores from an immature model (maturity gate not passed, 7 training rounds). Scores rank; they never assert a category.

Opus teacher head0.055
GPT teacher head0.271
Teacher spread0.216 · how far apart the two teachers sit on this one work
Validation statusscore_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from it

Classification

machine, unvalidated

Machine predicted; a candidate call from one source (direct Gemma or distilled Codex), not a consensus.

The models applied no category: nothing in the taxonomy fit this work.
Study designNot applicable
Domainnot available
GenreMethods

How this classification was reached, model by model and score by score, is at the end of the page under "How this classification was reached".

Quick stats

Citations5
Published2017
Admission routes1
Has abstractyes

Explore more

Same topicCloud Computing and Resource ManagementFrench-language works237,207