Demonstration venue · read-only. Every page can be browsed; the buttons that would change it are switched off. Create an account to run TaxoReview on your own data. A simulation from public publication records: the people listed were not invited and did not agree to review.
? Tutorial for this page

Jacek Becla

dblp:60/1926 · DBLP profile ↗
← Back
4ranked-venue papers
2as first author
0since 2021 · last 2009
—ORCID · none

Domains — the database's venue-derived domains; a paper can count in several

Databases, data management, data science and information retrieval · 3 · 1 first-authorSystems, architecture and hardware · 1 · 1 first-author

Expertise — from the expertise taxonomy: the topics of the expert's papers under the CCF categories. A weight counts papers with recency: 1 for a paper about the topic, 0.3 when the topic is its context, halved every five years.

Databases, data mining, and information retrieval
2 papers
Database system architecture and tuning · 61% Data models and query languages · 39%
Computer architecture, parallel and distributed computing, and storage systems
1 paper
Storage systems · 77% High-performance computing · 23%

Topics — the 3 heaviest of 5, each with the papers that count most for it

TopicWeightPapersLastEvidence papers
Database system architecture and tuning
scientific data management
0.012009
A Demonstration of SciDB: A Science-Oriented DBMS · Proc. VLDB Endow. 2009
Storage systems › data management › database storage
object-oriented database storage
0.012000
Creating Large Scale Database Servers · HPDC 2000
High-performance computing
scientific data management
0.012000
Creating Large Scale Database Servers · HPDC 2000

Methods — techniques the papers use, named apart from their topics

uncertainty and lineage support · 0.1regrid operations · 0.1
YearPublicationVenuePosition
2009 Requirements for Science Data Bases and SciDB
Michael Stonebraker, Jacek Becla, David J. DeWitt, Kian-Tat Lim, David Maier 0001, Oliver Ratzesberger, Stanley B. Zdonik
CIDR2
2009 A Demonstration of SciDB: A Science-Oriented DBMS
abstract
In CIDR 2009, we presented a collection of requirements for SciDB, a DBMS that would meet the needs of scientific users. These included a nested-array data model, science-specific operations such as regrid, and support for uncertainty, lineage, and named versions. In this paper, we present an overview of SciDB's key features and outline a demonstration of the first version of SciDB on data and operations from one of our lighthouse users, the Large Synoptic Survey Telescope (LSST).
Philippe Cudré-Mauroux, Hideaki Kimura 0001, Kian-Tat Lim, Jennie Rogers, Roman Simakov, Emad Soroush, Pavel E. Velikhov, Daniel L. Wang, Magdalena Balazinska, Jacek Becla, David J. DeWitt, Bobbi Heath, David Maier 0001, Samuel Madden 0001, Jignesh M. Patel, Michael Stonebraker, Stanley B. Zdonik
Proc. VLDB Endow.10
2005 Lessons Learned from Managing a Petabyte
Jacek Becla, Daniel L. Wang
CIDR1
2000 Creating Large Scale Database Servers
abstract
The BaBar experiment at the Stanford Linear Accelerator Center (SLAC) is designed to perform a high precision investigation of the decays of B-meson produced from electron-positron interactions. The experiment, started in May 1999, will generate approximately 300 TB/year of data for 10 years. All of the data will reside in objectivity databases (object oriented databases), accessible via the Advanced Multi-threaded Server (AMS). To date, over 70 TB of data have been placed in Objectivity/DB, making it one of the largest databases in the world. Providing access to such a large quantity of data through a database server is a daunting task. A full-scale testbed environment had to be developed to tune various software parameters and a fundamental change had to occur in the AMS architecture to allow it to scale past several hundred terabytes of data. Additionally, several protocol extensions had to be implemented to provide practical access to large quantities of data. The paper describes the design of the database and the changes that we needed to make in the AMS for scalability reasons and how the lessons we learned would be applicable to virtually any kind of database server seeking to operate in the Petabyte region.
Jacek Becla, Andrew Hanushevsky
HPDC1