Change Password

Please enter the password.
Please enter the password. Between 8-64 characters. Not identical to your email address. Contain at least 3 of: uppercase, lowercase, numbers, and special characters.
Please enter the password.
Submit

Change Nickname

Current Nickname:
Submit

Apply New License

License Detail

Please complete this required field.

  • Ultipa Graph V4

Standalone

Please complete this required field.

Please complete this required field.

The MAC address of the server you want to deploy.

Please complete this required field.

Please complete this required field.

Cancel
Apply
ID
Product
Status
Cores
Applied Validity Period(days)
Effective Date
Excpired Date
Mac Address
Apply Comment
Review Comment
Close
Profile
  • Full Name:
  • Phone:
  • Company:
  • Company Email:
  • Country:
  • Language:
Change Password
Apply

You have no license application record.

Apply
Certificate Issued at Valid until Serial No. File
Serial No. Valid until File

Not having one? Apply now! >>>

Product Created On ID Amount (USD) Invoice
Product Created On ID Amount (USD) Invoice

No Invoice

v5.0
Search
    English
    v5.0

      Indexing and Caching

      Ultipa offers several strategies to optimize query performance.

      Indexing. Indexes speed up property lookups by creating an index tree on disk, reducing the data scan required for retrieval and filtering. Ultipa also supports full-text indexing, which segments text and builds a reverse index, allowing for precise and fuzzy keyword matching. See Index and Full-text Index for details.

      Caching. Caching stores frequently accessed data in memory, minimizing disk access and improving query response times. In Ultipa, caching can be applied to various data types, including graph topology and LTE-ed properties. See LTE and Cache for details.

      Both indexes and caches in Ultipa are automatically updated to ensure that they reflect the most recent data. This helps maintain optimized query performance without requiring manual intervention for updates.

      Index vs. LTE

      A property can be indexed or LTE-ed to enhance performance. When selecting a strategy, consider their applicability in the following scenarios:

      Scenario
      Index LTE
      Filtering of nodes and edges in find().nodes() and find().edges() queries
      Filtering of start nodes
      Filtering of nodes and edges in other places

      You can apply both indexing and LTE strategies to certain properties based on your needs. However, it's important to consider the efficient use of disk and memory space on shard servers to avoid excessive resource consumption.

      Please complete the following information to download this book
      *
      公司名称不能为空
      *
      公司邮箱必须填写
      *
      你的名字必须填写
      *
      你的电话必须填写