The model takes ARM 64-bit assembly language blocks as input and provides a discrete probabilistic distribution for the execution time of the given block. The distribution can be used to sample mean execution time of the assembly code.
Highlights
Use the model to optimize your code based on the generated assembly, leveraging learned performance patterns
Predicts a probability distribution of execution time (in nanoseconds) for each block on the ARM Cortex-A53 core
Extracts key timing metrics: Mean, Standard Deviation (STD), Max, and Median to understand performance variability at the ASM level
AWS Marketplace now accepts line of credit payments through the PNC Vendor Finance program. This program is available to select AWS customers in the US, excluding NV, NC, ND, TN, & VT.
You pay by the hour for model inference running on the ml.g5.xlarge instance type. Billing is usage-based, so charges track the hours the instance runs. The two dimensions split by inference mode. Batch mode processes grouped requests together. Real-time mode handles requests as they arrive. Both use the same instance type, so your choice depends on how you send workloads, not on instance size. You can run either mode, and costs scale with host hours consumed.
Top-of-mind questions for buyers
What runs on the ml.g5.xlarge instance, and what does this model predict?
You run inference for a code-language model that predicts software execution behavior. It reads compiled binaries and predicts per-function timing, energy cost, throughput, and stack pressure ahead of runtime. The model covers ARMv8 AArch64 assembly. Billing tracks the instance hours consumed while inference runs.
How does batch mode inference differ from real-time mode on my bill?
Both modes meter host hours on the same ml.g5.xlarge instance. Batch mode groups multiple requests and processes them together, suiting large offline prediction jobs. Real-time mode handles requests one at a time as they arrive, suiting interactive use. Cost tracks the hours each mode runs, not the number of requests.
Am I charged when the instance is idle or stopped between inference jobs?
Software charges apply per host hour while the instance runs. A fully stopped instance does not accrue software charges. Stopped instances may still incur underlying AWS storage fees, but the software license meters running time only. To stop billing, shut down the instance when inference is not needed.
www.auroralabs.com
Helpful?
Vendor refund policy
no refunds
How can we make this page better?
Tell us how we can improve this page, or report an issue with this product.
Give us feedbackReport a problem with this product or seller
Legal
Vendor terms and conditions
Upon subscribing to this product, you must acknowledge and agree to the terms and conditions outlined in the vendor's End User License Agreement (EULA).
Content disclaimer
Vendors are responsible for their product descriptions and other product content. AWS does not warrant that vendors' product descriptions or other product content are accurate, complete, reliable, current, or error-free.
An Amazon SageMaker model package is a pre-trained machine learning model ready to use without additional training. Use the model package to create a model on Amazon SageMaker for real-time inference or batch processing. Amazon SageMaker is a fully managed platform for building, training, and deploying machine learning models at scale.
Deploy the model on Amazon SageMaker AI using the following options:
Real-time inference
Deploy the model as an API endpoint for your applications. When you send data to the endpoint, SageMaker processes it and returns results by API response. The endpoint runs continuously until you delete it. You're billed for software and SageMaker infrastructure costs while the endpoint runs. AWS Marketplace models don't support Amazon SageMaker Asynchronous Inference. For more information, see Deploy models for real-time inference .
Batch transform
Deploy the model to process batches of data stored in Amazon Simple Storage Service (Amazon S3). SageMaker runs the job, processes your data, and returns results to Amazon S3. When complete, SageMaker stops the model. You're billed for software and SageMaker infrastructure costs only during the batch job. Duration depends on your model, instance type, and dataset size. AWS Marketplace models don't support Amazon SageMaker Asynchronous Inference. For more information, see Batch transform for inference with Amazon SageMaker AI .
Version release notes
Initial release for Amazon Sagemaker
Additional details
Inputs
Outputs
Usage instructions
Sample notebooks
Inputs
Summary
The input has to be a csv file, with one column named 'r.asm'. Each row can be assembly code based on the ARMv8 aarch64 architecture.
The code snippet below shows how to load the data in Python using the pandas package.
data = pandas.read_csv('../data/arm_dataset.csv')
More detailed example is available in the Jupyter notebooks.
Limitations for input type
The csv file should have less than 2000 rows, for optimal performance. It is recommended that the length of one sample of assembly code is not longer than 500 instructions.
AWS Support is a one-on-one, fast-response support channel that is staffed 24x7x365 with experienced and technical support engineers. The service helps customers of all sizes and technical abilities to successfully utilize the products and features provided by Amazon Web Services.
The Loci-Stream CFD code is a scalable parallel tool for fluid-flow and heat transfer simulations in large scale industrial applications. Many of the common features found in other standard CFD tools such as ANSYS-Fluent and Star-CCM+ are available. If you are interested in testing Loci-Stream, see the tutorials page on our website which contains run control and grid files for a number of cases that can be run directly.
LOCI, Line-of-Code Intelligence platform, transforms observability and shift-left approach by extracting deep performance insights from compiled binaries (e.g., C/C++, Go, Rust), without requiring source code. Traditional static analysis and observability tools fail to detect performance issues in compiled BIN files due to missing execution context, hardware interactions, and real-time software behavior analysis. LOCI bridges this gap by modeling compiled binaries with real-world execution data, enabling early detection of performance degradations, power inefficiencies, and test coverage prediction, after project build.
Be the first to review this product. We've partnered with PeerSpot to gather customer feedback. You can share your experience by writing or recording a review, or scheduling a call with a PeerSpot analyst.