Memory Configuration

The Memory settings page allows you to configure how your ChatNexus chatbot retains and manages conversation history and context.

Settings navigation

Core Memory Settings

Include Memory Toggle

Enable or disable the chatbot's ability to remember past interactions:

  • Yes: Chatbot maintains conversation context
  • No: Each interaction is treated independently
  • Impact on response relevance and personalization
  • Affects token usage and processing speed

Memory Type Selection

Currently supports:

  • ConversationSummaryBufferMemory
  • Maintains condensed conversation history
  • Optimizes token usage through summarization
  • Balances context retention with performance
  • Best for most use cases

Configuration Parameters

Memory History

  • Set the number of conversation turns to retain
  • Default: 10 turns
  • Considerations:
  • Higher values provide better context
  • Lower values reduce token usage
  • Recommended range: 5-15 turns
  • Adjust based on conversation complexity

Chat Storage Duration

  • Define how long to store chat histories
  • Default: 365 days
  • Key factors:
  • Compliance requirements
  • User experience needs
  • Storage costs
  • Data privacy policies

Best Practices

Memory Optimization

  1. Context Length
  • Balance depth vs. performance
  • Consider typical conversation patterns
  • Monitor token usage
  • Test different history lengths
  1. Storage Management
  • Regular cleanup of old conversations
  • Implement data retention policies
  • Monitor storage usage
  • Consider compliance requirements

Use Case Recommendations

  1. Customer Support
  • Memory History: 8-10 turns
  • Storage Duration: 90-365 days
  • Enable summarization
  1. Technical Support
  • Memory History: 12-15 turns
  • Storage Duration: 180-365 days
  • Detailed context retention
  1. General Inquiries
  • Memory History: 5-8 turns
  • Storage Duration: 30-90 days
  • Light summarization

Performance Impact

Memory Usage

  • More turns = higher token consumption
  • Longer storage = increased database usage
  • Summarization helps optimize costs
  • Monitor performance metrics

Optimization Tips

  1. Token Usage
  • Start with lower memory turns
  • Increase gradually as needed
  • Monitor response quality
  • Balance cost vs. context
  1. Storage Efficiency
  • Regular archiving
  • Compression strategies
  • Cleanup automation
  • Backup procedures

Troubleshooting

Common issues and solutions:

  1. Context Loss
  • Increase memory turns
  • Check summarization settings
  • Verify memory type configuration
  • Test conversation flow
  1. Performance Issues
  • Reduce memory turns
  • Enable summarization
  • Optimize storage duration
  • Clear old chat histories

Implementation Guide

  1. Initial Setup
  • Enable memory feature
  • Select memory type
  • Set initial history length
  • Configure storage duration
  1. Testing
  • Verify context retention
  • Check response relevance
  • Monitor performance
  • Adjust as needed

Remember to click "Save" after adjusting any memory settings to ensure your changes are applied.