Organizations

Resources

Introduction

Organizations can subscribe to hardware resources to run backtests, launch research notebooks, and deploy live trading algorithms to co-located servers. Organizations also have access to storage resources via the ObjectStore to store data between backtests or live trading deployments. To promote efficiency, all of these resources within your organization are shared among all of the members within the organization. A team of several quants can all share one backtest, research, and live trading node.

Backtesting Nodes

Backtesting nodes enable you to run backtests. The more backtesting nodes your organization has, the more concurrent backtests that you can run. Several models of backtesting nodes are available. Backtesting nodes that are more powerful can run faster backtests and backtest nodes with more RAM can handle more memory-intensive operations like training machine learning models, processing Options data, and managing large universes. The following table shows the specifications of the backtesting node models:

TypeNumber of CoresProcessing Speed (GHz)RAM (GB)
B-MICRO238
B2-824.98
B4-1244.912
B8-1684.916

Refer to the Pricing page to see the price of each backtesting node model. You get one free B-MICRO backtesting node in your first organization. This node incurs a 20-second delay when you launch backtests, but the delay is removed and the node is replaced when you subscribe to a new backtesting node in the organization. Backtesting nodes are offered on a fair usage basis and can't be used for optimization.

Research Nodes

Research nodes enable you to use the Research Environment. Several models of research nodes are available. More powerful research nodes allow you to handle more data and run faster computations in your notebooks. The following table shows the specifications of the research node models:

TypeNumber of CoresProcessing Speed (GHz)RAM (GB)
R1-412.44
R2-822.48
R4-1242.412
R8-1682.416

Refer to the Pricing page to see the price of each research node model. You get one free R1-4 research node in your first organization, but the node is replaced when you subscribe to a new research node in the organization.

Live Trading Nodes

Live trading nodes enable you to deploy live algorithms to the co-located servers. Several models of live trading nodes are available. More powerful live trading nodes allow you to run algorithms with larger universes and give you more time for machine learning training. The following table shows the specifications of the live trading node models:

TypeNumber of CoresProcessing Speed (GHz)RAM (GB)
L-MICRO12.60.5
L1-112.61
L1-212.62
L1-412.64

Refer to the Pricing page to see the price of each live trading node model.

Sharing Resources

Your organization's nodes are shared among all of the organization's members to reduce the amount of time that nodes idle. In the Algorithm Lab, you can see which nodes are available within your organization. By default, the best-performing resource is selected when you run a backtest or launch a research notebook, but you can select a specific resource to use.

Node Quotas

The following table shows the number of nodes each organization tier can have:

TierBacktestResearchLive Trading
Free110
Quant Researcher212
Team101010
Trading FirmInf.Inf.Inf.
InstitutionInf.Inf.Inf.

Training Quotas

Algorithms normally must return from the OnData method within 10 minutes, but the Train method lets you increase this amount of time. Training resources are allocated with a leaky bucket algorithm where you can use a maximum of n-minutes in a single training session and the number of minutes available refills over time. This gives you a reservoir of training time when you need it and recharges the reservoir to prepare for the next training session. The reservoir only starts draining after you exceed the standard 10 minutes of training time.

The following animation demonstrates the leaky bucket algorithm. The tap continuously adds water to the bucket. When the bucket is full, water spills over the rim of the bucket. The water represents your training resources. When your algorithm exceeds the 10 minutes of training time, holes open at the bottom of the bucket and water begins to drain out. When your algorithm stops training, the holes close and the bucket fills up with water.

The following table shows the amount of extra time that each backtesting and live trading node can spend training machine learning models:

ModelCapacity (min)Refill Rate (min/day)
B-MICRO201
B2-8305
B4-126010
B8-169015
L-MICRO305
L1-16010
L1-29015
L1-412020

The refill rate in the table above is based on the real-world clock time, not the backtest clock time. In backtests, the Train method is synchronous, so it will block your algorithm from executing while the model is trained. In live trading, the method runs asynchronously, so ensure your model is ready to use before you continue executing the algorithm. Training occurs on a separate thread, so use a semaphore to track the model state.

Log Quotas

By our Terms and Conditions, you may not use the logs to export dataset information. The following table shows the amount of logs each organization tier can produce:

TierLogs Per Backtest
Logs Per Day
Free
10KB3MB
Quant Researcher
100KB3MB
Team
1MB10MB
Trading Firm
5MB50MB
Institution
Inf.Inf.

If you delete a backtest or project that produced logs, your quotas aren't restored. Additionally, daily log quotas aren't fully restored at midnight. They are restored according to a 24-hour following window.

The log files of each project can store up to 100,000 lines for up to one year. If you log more than 100,000 lines or some lines become older than one year, we remove the oldest lines in the files so your project stays within the quota.

To avoid reaching the limits, we recommend logging sparsely, focusing on the change events instead of logging every time loop. You can use the debugger to inspect objects during runtime. If you use the debugger, you should rarely reach the log limits.

Coding Session Quotas

If you have a project open, it uses a coding session. Your account can have up to one coding session across all of your free organizations. If you connect as a paid organization, your account can have multiple active coding sessions. The following table shows how many active coding sessions you can have on each organization tier:

TierInitial Coding Session Quota
Quant Researcher2
Team4
Trading Firm8
Institution16

If the organization you're in has more live trading nodes than your initial coding session quota, then your coding session quota increases to the number of live trading nodes you have in the organization.

The quota for free organizations is a global quota, so you can have one active coding session across all of your free organizations. The quotas for paid organizations are at the organization level. Therefore, if you are in two Quant Researcher organizations, you can have two active coding sessions in one of those organizations and another two active sessions in the other organization. These paid tier quotas are for each account, not for the organization as a whole. For instance, a Trading Firm organization can have more than eight members and all of the members can simultaneously work on projects within the organization.

View All Nodes

The Resources page displays your backtesting, research, and live trading node clusters. To view the page, log in to the Algorithm Lab and then, in the left navigation bar, click Organization > Resources.

To toggle the format of the page, click the buttons in the top-right. If the page is in table view, each cluster section includes a table with the following columns:

ColumnDescription
NameName of the node
Machine TypeThe node model and specifications
In Use ByThe name of the member using the node
HostThe live trading server name
AssetsThe recommended maximum number of assets to avoid RAM errors.
ActionsA list of possible actions

Add Nodes

You need billing permissions in the organization to add nodes.

Follow these steps to add nodes to your organization:

  1. Open the Resources page.
  2. Click Add nodeType Node for the type of node you want to add.
  3. Select the node specifications.
  4. Click Add Node.
  5. The Resources page displays the new node.

Remove Nodes

You need billing permissions in the organization to remove nodes. If you remove nodes during your billing period, your organization will receive a pro-rated refund.

Follow these steps to remove nodes from your organization:

  1. Log in to the Algorithm Lab.
  2. In the left navigation bar, click Organization > Home.
  3. On the organization homepage, click Edit Plan.
  4. Click the Customize Plan > Build Your Own Pack > Compute Nodes tab.
  5. Click the minus sign next to the node model you want to remove.
  6. Click Proceed to Checkout.

Rename Nodes

We assign a default name to hardware nodes that includes the model name and an arbitrary string of characters, but you can follow these steps to rename the nodes in your organization:

  1. Open the Resources page.
  2. Click Set Name on the node that you want to rename.
  3. Enter the new node name and then click Save Changes.
  4. The Resources page displays the new node name.

Stop Nodes

You need stop node permissions in the organization to stop nodes other members are using.

Follow these steps to stop nodes that are running in your organization:

  1. Open the Resources page.
  2. Click the icon with the three horizontal lines icon in the top-right corner to format the page into table view.
  3. Click Stop in the row with the node that you want to stop.

You can also see our Videos. You can also get in touch with us via Discord.

Did you find this page helpful?

Contribute to the documentation: