Datagrip Redis Introspection large number of strings and introspection not finishing

Hi,
I’ll copy here some information we discussed in the support ticket:

I have read introspection is the fact of inventoring data. Is introspecting essential?. Can't it be avoided?

Introspection is a process of loading metadata of a database. When you perform introspection, structural information in the data source is inspected to detect tables, columns, routines, and other database objects with their attributes. Technically, you can cancel the introspection and disable the auto-sync setting so it’s not triggered automatically. However, introspection is necessary for DataGrip to show the objects, enable code completion, and more.

I just wanted to have a clear way of looking redis data in a strings schema of 3.000.000 of strings.

While we’ve recently improved introspection performance for Redis (these changes should be in DataGrip 2025.1.3), it will still take some time to introspect 3 million strings. Some common ways to improve introspection speed in Redis include:

1. Add a Default key filter setting where you can specify which keys should be introspected (see the General tab settings section).
2. Filter the databases, as outlined in the Redis Support post.

Perhaps can memory increase for Java decrease introspection time?. Should I apply any kind of change?

You can increase the memory, but with 3 million keys, it will still take time. You can increase the IDE’s memory as outlined in the Increase the memory heap of the IDE article.

I will also be looking forward to your response in the corresponding support ticket.