Error: TimedOut

[zqlpaopao]

If I set this parameter very high, there is a chance of reporting a timeout, but if I set it too small, the data may not be returned

   transport_configuration.set_max_buf_size(1024*1024*100000);
    transport_configuration.set_buf_size(1024*1024*10000);
    transport_configuration.set_read_timeout(Duration::from_millis(1000000000000000).as_secs() as u32 );
    

Error: TimedOut

[vkill]

transport_configuration.set_max_buf_size(1024*1024*4);
transport_configuration.set_buf_size(1024*1024*2);
transport_configuration.set_read_timeout(30000);
transport_configuration.set_max_parse_response_bytes_count(64);

@zqlpaopao I think this configuration is completely enough.

[zqlpaopao]

transport_configuration.set_max_buf_size(1024*1024*4);
transport_configuration.set_buf_size(1024*1024*2);
transport_configuration.set_read_timeout(30000);
transport_configuration.set_max_parse_response_bytes_count(64);

@zqlpaopao I think this configuration is completely enough.
called Result::unwrap() on an Err value: ThriftError(Reach max parse response bytes count

If I use this configuration when the quantity is large or when there are over 30000 points and many edges. Due to insufficient memory, it is common to set a large amount of memory in advance to prevent issues. However, setting it too high can lead to problems. How can one measure the number of their Nebula graphs

[vkill]

Are the program and NebulaGraphQL running on the same LAN?
Maybe you have a lot of query results. How about pagination?