Pith. sign in

REVIEW

Sun Microsystem's AutoClient and management of computer farms at BaBar

Not yet reviewed by Pith; the record is open.

This paper has not been read by Pith yet. Machine review is queued; the pith claim, tier, and objections will appear here once it completes.

SPECIMEN: schema-true, not a live event

T0 review · schema-true

One-sentence machine reading of the paper's core claim.

pith:XXXXXXXX · record.json · timestamp

arxiv physics/0001041 v1 pith:QUYR7W4J submitted 2000-01-20 physics.comp-ph physics.gen-ph

classification physics.comp-phphysics.gen-ph
keywords autoclientsystemsavailablebabarbeenfarmsmanagementperformance
verification ladder T0 review T1 audit T2 compute T3 formal

Signed reviews

No signed human review yet.

0 comments
read the original abstract

Modern HEP experiments require immense amounts of computing power. In the BaBar experiment at SLAC, most of it is provided by Solaris SPARC systems. AutoClient, a product of Sun Microsystems, was designed to make setting up and managing large numbers of Solaris systems more straightforward. AutoClient machines keep all filesystems, except swap, on a server and employ CacheFS to cache them onto a local disk, which makes them Field Replaceable Units with performance of stand-alone systems. We began exploring the technology in Summer 1998, and currently operate online, reconstruction, analysis and console AutoClient farms with the total number of nodes exceeding 400. Although the technology has been available since 1995, it has not been widely used, and the available documentation does not adequately cover many important details of AutoClient installation and management. This paper discusses various aspects of our experience with AutoClient, including tips and tricks, performance and maintainability, scalability and server requirements, existing problems and possible future enhancements.

Discussion (0). Continue with ORCID to comment.

Pith tools