MétaCan
Menu
Back to cohort
Record W2169177888 · doi:10.1109/pccc.1998.659903

The effect of object-agent interactions on the performance of CORBA systems

2002· article· en· W2169177888 on OpenAlex

Why this work is in the frame

A frame that forgets how it found something cannot be audited. These are the routes that admitted this work.

affAt least one author lists a Canadian institution in the pinned OpenAlex snapshot.

Bibliographic record

Venuenot available
Typearticle
Languageen
FieldComputer Science
TopicMobile Agent-Based Network Management
Canadian institutionsCarleton UniversityNortel (Canada)
Fundersnot available
KeywordsCommon Object Request Broker ArchitectureComputer scienceObject request brokerOrb (optics)Middleware (distributed applications)ScalabilityServerInteroperabilityClient–server modelDistributed computingInteroperable Object ReferenceWorkstationArchitectureOperating systemDistributed object

Abstract

fetched live from OpenAlex

The notion of middleware has been introduced to provide interoperability as well as transparent location of servers in heterogeneous client server environments. Although such benefits accrue from the use of middleware, careful consideration of system architecture is required to achieve high performance. Based on implementation and measurements made on the system, the paper is concerned with the impact of client agent server interaction architecture on the performance of a CORBA System. CORBA or Common Object Request Broker Architecture proposed by the Object Management Group is one of the commonly used standards for middleware architecture. Using a commercially available CORBA compliant ORB software called ORBeline, we have implemented two different architectures for client agent server interaction on a network of workstations. In the Handle Driven ORB architecture the client gets the address of the server from the agent and communicates with the server directly. In the Forwarding ORB architecture the client request is automatically forwarded by the agent to the appropriate server which then returns the results of the computations to the client. Our measurements show that the differences among the performance of these architectures change with a change in the workload. The paper reports on the relative performance of the two architectures under different workload conditions. The results provide insights into system behavior. In particular the impact of message size on the latency and scalability attributes of these architectures is analyzed. A discussion of how agent cloning can improve system performance is also included.

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.

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.001
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: Simulation or modeling · Consensus signal: none
GenreCandidate signal: Empirical · Consensus signal: Empirical
Teacher disagreement score0.765
Threshold uncertainty score0.182

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0010.000
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0000.000
Bibliometrics0.0000.000
Science and technology studies0.0000.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.014
GPT teacher head0.215
Teacher spread0.201 · 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

Quick stats

Citations4
Published2002
Admission routes1
Has abstractyes

Explore more

Same topicMobile Agent-Based Network ManagementFrench-language works237,207