Autoclosing is a good take.

Depending on the userbase (e.g. end users from non-OSS ecosystems) and what you want to achieve you might just have to accept they are more used to talking to corporate support agents than filing bugs and learn to work with them. Autoclosing immediately puts the user into an adversarial position - better would be to have an automated reply for incomplete bug reports stating what is missing and that the information is needed for you to help the user to make it clear that filling it in properly is in their best interest as well.

Thanks for your feedback and sorry for the user experience. Is there an element that you feel specifically hard to read? For example, code snippet?

Are you reading on mobile? As to "the share hover", do you mean the popup?

Graph databases are efficient in exploring multi-hop relationships which are common in many business scenarios. So basically if your application needs to query n-hop relationships all the time, then graph database is a better choice. Some main use cases include real-time recommendation (product/content/shop), risk management like fraud detection in the financial services industry, knowledge graph and machine learning, etc.

Good point. Software systems mature with on-going testing. Nebula Graph has implemented Jepsen tests for quite some time already. See https://nebula-graph.io/en/posts/detect-data-consistency-iss...

That is really good then! I’ll check it out now

Thanks for sharing! Yes you are right, the architecture articles are trying to help users understand how Nebula Graph stores and processes data.

Great digging! Thanks so much for paying attention to the benchmark report data. We apologize that you have to wait for so long!

Yes we have been working on the benchmark data for quite some time because we have been working with our clients to verify our capability. For example, one of our clients has inserted 300b records to 6 servers within 20 hours, then we are confident to say that Nebula Graph can manage 690k inserts/sec/server.

We will keep working and provide a trustworthy benchmark report for you as soon as we can.

Thanks again!

Thanks so much for your suggestion regarding the website!I am thinking about the same thing as well. Will keep improving the site along the way. Really appreciate it.

As to the data for throughput, there are some PoC projects going on and according to data from production, for inserting, one of our clients has inserted 300b records to 6 servers within 20 hours, that is 690k inserts/sec/server.

We want the benchmark data to be verified by decent clients in their production environment. And will reveal more data in the future.

Thanks again!

Just curious, didn’t you have to do some basic benchmarking using your own data to get these clients to signup in the first place? Or is this part of a larger engagement/partnership that these clients trust you enough to embark on this?

Thanks for your advice! Appreciate that. I'll try my best.

Nice to know the site. I found Hootsuite is also a nice place to manage a Twitter handle.

Totally agree that the nice thing is everything stays in one place. I use it for Stack Overflow as well. :) And will definitely add Reddit to my list.