> ## Documentation Index
> Fetch the complete documentation index at: https://www.helius.dev/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Solana Dedicated Nodes Best Practices: Optimize Performance

> Optimize your Solana dedicated node performance with best practices for gRPC streaming, load management, and node health monitoring.

## Best Practices

### Primary Use: gRPC Streaming

**Dedicated nodes are optimized for gRPC streaming applications**. For the best experience:

* **Use with Yellowstone Geyser Plugin**: This is the primary and recommended use case for dedicated nodes
* **Combine with a shared plan**: For `sendTransaction`, archival data, and complex account queries, use your shared plan endpoints
* **Focus on streaming**: Leverage dedicated nodes for real-time data streaming, monitoring, and analytics

### Managing Node Load

While nodes don't have strict usage limits, they are bound by hardware constraints. A balanced workload helps maintain optimal performance and node liveliness.

* **Use [`getProgramAccounts`](/api-reference/rpc/http/getprogramaccounts) carefully**: While supported, dedicated nodes are not optimized for these calls - heavy usage can impact performance or cause node failure
  * Use your shared plan for `getProgramAccounts` queries as we have a [**custom indexer**](https://x.com/helius/status/1864750969755422797) that makes gPA calls much faster and more reliable. Shared plans also support `getProgramAccountsV2`, which adds support for pagination and incremental updates.
* **Poor transaction landing rates**: While [`sendTransaction`](/api-reference/rpc/http/sendtransaction) is supported, it's not optimized - most transactions will not land; use your shared plan or [Sender](/sending-transactions/sender) for landing Solana transactions more reliably
* Monitor your node's metrics to understand its performance based on response times, successful request %, and error counts
* Consider distributing intensive workloads across multiple nodes in a dedicated fleet

### What's Not Supported

Dedicated nodes do not support the following features. Use your shared paid plan for these capabilities:

* **[Historical data](/rpc/historical-data)**: No archival data access
* **Platform APIs**: No access to platform-specific APIs
* **Webhooks**: Webhook functionality not available
* **Staked connections**: No staked connection support

<Note>
  If your team needs a cluster of multiple dedicated nodes, [contact our sales team](https://www.helius.dev/contact). We will take in your requirements and configure a dedicated fleet for your team.
</Note>

### System Recovery

Our nodes include an automatic recovery mechanism:

* If a node falls too far behind in processing slots, it will automatically initiate a restart
* During this recovery period, all requests are seamlessly routed to our shared backup pool
* Once your node catches up and becomes healthy, traffic will resume to it

### Questions and Support

* Contact us through your Telegram group (available for dedicated node customers)
* You can also get support from the chat system on our website or in our Discord server