enable_remote_cache_accessible
Applicability
Product |
Supported (√/x) |
|---|---|
Atlas 350 Accelerator Card |
x |
√ |
|
√ |
|
x |
|
x |
|
x |
Note: For
Function Description
Specifies whether to enable the function of directly accessing the remote cache.
When this parameter is enabled, the remote cache metadata (such as index and memory address) is cached locally to accelerate the pull process. However, this also introduces relevant restrictions. For details, see Restrictions.
Prototype
1 | enable_remote_cache_accessible(self, enable_remote_cache_accessible: bool) |
Parameters
Parameter |
Data Type |
Description |
|---|---|---|
enable_remote_cache_accessible |
bool |
Whether to enable the function of directly accessing the remote cache. The options are as follows:
This function is disabled by default. |
If this parameter is disabled,
Example
1 2 3 | from llm_datadist import LLMConfig llm_config = LLMConfig() llm_config.enable_remote_cache_accessible = True |
Returns
In normal cases, no value is returned.
If a parameter is incorrect, a TypeError or ValueError may be thrown.
Restrictions
The index update is triggered only during the first pull. Subsequent cache operations on the remote side are not visible to the local side after that. Therefore, you need to ensure the validity of the cache. This parameter is more suitable for the PagedAttention scenario, where caches are allocated and registered only during the initialization phase of the user script and do not change frequently.