MétaCan
Menu
Back to cohort
Record W69059961

Ultra-large scale services

2012· article· en· W69059961 on OpenAlexaffabout
Patrick Martin, Farhana Zulkernine

Bibliographic record

VenueConference of the Centre for Advanced Studies on Collaborative Research · 2012
Typearticle
Languageen
FieldComputer Science
TopicDistributed and Parallel Computing Systems
Canadian institutionsQueen's University
Fundersnot available
KeywordsScale (ratio)Computer scienceGeography
DOInot available

Abstract

fetched live from OpenAlex

Ultra-large-scale (ULS) services are extremely large software systems across all dimensions, such as the size of their code base, the number of users, the amount of data transferred, the number of developers, and the infrastructure for running these services. ULS services are at the core of many current Web 2.0 applications and are the building blocks of future Web 3.0 applications. ULS services provide the facilities needed for communication (the BlackBerry platform and the Rogers or Bell wireless networks), international banking (Interac and Visa), e-commerce (the eBay auction system and the Amazon Elastic Compute Cloud), social communities (Facebook and MySpace), massive multiplayer online games (World of Warcraft) and future e-healthcare deployments (Health Canada's Infostructure). ULS services are causing a revolution in computing. The scale of ULS services is often hard to grasp. Current ULS services are composed of thousands of hardware nodes; petabytes of data in databases; billions of lines of code, and millions of stakeholders. The Software Engineering Institute (SEI at Carnegie Mellon) report, Ultra-Large-Scale Systems: The Software Challenge of the (June 2006), highlighted the dire need for unique and modern approaches to cope with the scale, the wide and varied worldwide user base, the frequent failures and the evolving requirements of these systems. The National Science Foundation (NSF) and the UK Engineering and Physical Sciences Research Council (EPSRC) who recently established research and training centres for Ultra-Large-Scale Software Intensive Systems have heard these sentiments. More recently (2010), the IEEE Future Directions Committee highlighted the need for a shift within IEEE to cater to this critical and important domain. Research on a variety of challenging topics is needed to ensure that ULS services can be created and managed reliably in a cost-effective manner. Figure 1: Delivering Ultra Large Scale Services (ULSS) Figure 1 presents the four main perspectives of an efficient ULS service namely, the Focused Quality, Flexible Delivery, Scalable Quality, and Adaptive Infrastructure. Focused Quality implies delivering high quality ULS services, which is a top priority for all service providers. However, the characteristics of ULS services make this a very challenging and complex goal to achieve. The dynamic nature of ULS services (being composed of many other ULS services) and their large and varied user base (often consisting of millions of users with varying needs and expectations) increase the complexity of ensuring the quality of ULS services. For instance, it is impossible to test and verify every possible configuration and usage pattern as these configurations and patterns are continuously changing. This situation has led many ULS providers to depend heavily on monitoring approaches as a way to monitor the quality of their ULS services post-release. However, quality issues should be addressed early, rather than delayed until post-release where quality improvement options are very limited and costly. Techniques and approaches are needed to assist practitioners in focusing their limited resources on the quality improvement efforts which have the highest return, that is, those that are most likely to improve the customer experience. In the world of ULS services, services must handle millions of users with varying needs and capabilities; which is why flexible delivery is recognized as an important aspect. For example, a medical remote diagnostic service that is part of Health Canada's Infostructure might be used by a senior citizen with limited knowledge about medical terms and options, or by a seasoned emergency response worker who requires a more elaborate tool to support his decision making. Providing a single service to satisfy the needs of both users is not feasible today. Instead, different services must be created and maintained. Moreover users of such a medical service might need to perform resource-intensive operations (e.g., watching videos or performing complex simulations based on inputted data), these operations must be delivered in flexible manner instead of simply performing all the operations either locally or centrally (i.e., at the data center). ULS Services need to support both flexible personalization of the service and access through a variety of devices, including smart phones and tablets, in order to accommodate all potential users. ULS systems provide computing, storage and abstraction services, allowing applications to access services with limited knowledge of, expertise with, or control over, the technology infrastructure that supports them. For example, the Blackberry platform connects the wired and wireless internet infrastructure to enable the seamless integration of enterprise and entertainment services between both types of networks. ULS systems are deployed at a worldwide scale and most systems provide an application programming interface (API) to extend various functionalities. These APIs create an ecosystem through which ULS systems grow their user base. However, this leads to varying and innovative usage patterns that must be taken into account, increasing the impact of the reliability of ULS systems while also increasing the complexity of ensuring such reliability. Current industrial approaches to cope with the characteristics of ULS services ensure that they are of high quality but are usually ad hoc, last-resort efforts. Principled approaches are needed to provide scalable high quality services and to evolve these services in an efficient manner while handling their continuously growing user base. For example, current monitoring approaches must be enhanced and adapted to deal with the characteristics of ULS services; current testing techniques and approaches must be revised based on an understanding of the impact of very large user bases on the performance and correctness of software systems in general and ULS service in particular, and traditional security approaches must be adapted to cope with the complexity of ULS services and their evolving usage. To remain competitive, the cost of providing ULS services must scale well with new users and/or units are added. Some ULS providers advocate the need for sub-linear growth in cost, that is, the cost per user/unit should decrease as more users are added to their services. Given the vast number of users, the fluctuation in workload intensities and complexities, the large number of services that must be supported and the unprecedented volumes of different types of data to be processed, it is imperative that ULS infrastructures, on which ULS services run, adapt to the growth, expansion and ever-increasing demands placed on them. The infrastructures, therefore, need to provide autonomic management of the resources, elastic provisioning of storage and other resources to services and support for high availability.

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 distilled prediction

Teacher imitation

Not calibrated prevalence, not ground truth. Human validation pending. Learned from the 10,348 direct Codex labels and 10,348 direct Gemma labels. Candidate is the union of thresholded teacher heads; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels or direct frontier model labels.

metaresearch head score (Codex)0.002
metaresearch head score (Gemma)0.000
Version: codex-gemma-dda1882f352aValidation status: machine_predicted_unvalidated
Candidate categoriesnone
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Theoretical or conceptual · Consensus signal: none
GenreCandidate signal: Empirical · Consensus signal: Empirical
Teacher disagreement score0.779
Threshold uncertainty score0.520

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0020.000
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0000.000
Bibliometrics0.0000.001
Science and technology studies0.0010.000
Scholarly communication0.0000.000
Open science0.0010.000
Research integrity0.0000.000
Insufficient payload (model declined to judge)0.0000.000

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.087
GPT teacher head0.395
Teacher spread0.308 · 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 teacher head, not a consensus.

The models applied no category: nothing in the taxonomy fit this work.
Study designTheoretical or conceptual
Domainnot available
GenreEmpirical

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

Citations0
Published2012
Admission routes2
Has abstractyes

Explore more

Same venueConference of the Centre for Advanced Studies on Collaborative ResearchSame topicDistributed and Parallel Computing SystemsFrench-language works237,207