About: Which of My Transient Type Checks Are Not (Almost) Free?

Not logged in : Login

(Sponging disallowed)

Facets (new session)
Description
Metadata
Settings
- Rule:
- Inverse Functional Properties:
- "Same As":

About: Which of My Transient Type Checks Are Not (Almost) Free? Goto Sponge NotDistinct Permalink

An Entity of Type : bibo:AcademicArticle, within Data Space : demo.openlinksw.com associated with source document(s)

Attributes	Values
type	http://eprints.org/ontology/ConferenceItemEPrint http://eprints.org/ontology/EPrint Article Academic Article
seeAlso	HTML Summary of #77492 Which of My Transient Type Checks Are Not (Almost) Free?
sameAs	Which of My Transient Type Checks Are Not (Almost) Free?
http://eprints.org/ontology/hasAccepted	Which of My Transient Type Checks Are Not (Almost) Free? (PDF)
http://eprints.org/ontology/hasDocument	Which of My Transient Type Checks Are Not (Almost) Free? (PDF) Which of My Transient Type Checks Are Not (Almost) Free? (Other) Which of My Transient Type Checks Are Not (Almost) Free? (Other) Which of My Transient Type Checks Are Not (Almost) Free? (Other) Which of My Transient Type Checks Are Not (Almost) Free? (Other) Which of My Transient Type Checks Are Not (Almost) Free? (Other)
dc:hasVersion	Which of My Transient Type Checks Are Not (Almost) Free? (PDF)
Title	Which of My Transient Type Checks Are Not (Almost) Free?
described by	https://demo.openlinksw.com/about/id/entity/https/www.cs.kent.ac.uk/people/staff/akj22/materials/CO644/export_kar_RDFN3.n3
Date	2019-10-20
Creator	Isaac Oscar Gariano James Noble Michael Homer Richard Roberts Stefan Marr
status	peer reviewed published
Publisher	ACM
abstract	One form of type checking used in gradually typed language is transient type checking: whenever an object ‘flows’ through code with a type annotation, the object is dynamically checked to ensure it has the methods required by the annotation. Just-in-time compilation and optimisation in virtual machines can eliminate much of the overhead of run-time transient type checks. Unfortunately this optimisation is not uniform: some type checks will significantly decrease, or even increase, a program’s performance. In this paper, we refine the so called “Takikawa” protocol, and use it to identify which type annotations have the greatest effects on performance. In particular, we show how graphing the performance of such benchmarks when varying which type annotations are present in the source code can be used to discern potential patterns in performance. We demonstrate our approach by testing the Moth virtual machine: for many of the benchmarks where Moth’s transient type checking impacts performance, we have been able to identify one or two specific type annotations that are the likely cause. Without these type annotations, the performance impact of transient type checking becomes negligible. Using our technique programmers can optimise programs by removing expensive type checks, and VM engineers can identify new opportunities for compiler optimisation.
Is Part Of	VMIL 2019 Proceedings of the 11th ACM SIGPLAN International Workshop on Virtual Machines and Intermediate Languages https://kar.kent.ac.uk/id/repository
list of authors	https://kar.kent.ac.uk/id/eprint/77492#authors
presented at	11th ACM SIGPLAN International Workshop on Virtual Machines and Intermediate Languages
is topic of	https://www.cs.kent.ac.uk/people/staff/akj22/materials/CO644/export_kar_RDFN3.n3
is primary topic of	HTML Summary of #77492 Which of My Transient Type Checks Are Not (Almost) Free?

Faceted Search & Find service v1.17_git144 as of Jul 26 2024

Alternative Linked Data Documents: iSPARQL | ODE Content Formats:

RDF

ODATA

Microdata

About

OpenLink Virtuoso version 08.03.3331 as of Aug 25 2024, on Linux (x86_64-ubuntu_noble-linux-glibc2.38-64), Single-Server Edition (378 GB total memory, 48 GB memory in use)
Data on this page belongs to its respective rights holders.
Virtuoso Faceted Browser Copyright © 2009-2024 OpenLink Software