After switching to Cluster Tier M10 (2 GB RAM, 8 GB Storage)
640 IOPS, 10 MB/s Throughput, Encrypted, Auto-expand Storage, the execution results are as follows:
[2025-05-19 02:55:52.1448192][ConnectionSendingMessagesEvent]
[2025-05-19 02:55:52.1508174][ConnectionSentMessagesEvent]Duration: 00:00:00.0014695, NetworkDuration: 00:00:00.0011434, SerializationDuration: 00:00:00.0003261
[2025-05-19 02:55:52.1514331][ConnectionReceivingMessageEvent]
[2025-05-19 02:55:52.1675920][ConnectionReceivedMessageEvent]Duration: 00:00:00.0160149, NetworkDuration: 00:00:00.0160008, DeserializationDuration: 00:00:00.0000141
[2025-05-19 02:55:52.1762076][ConnectionSendingMessagesEvent]
[2025-05-19 02:55:52.1766731][ConnectionSentMessagesEvent]Duration: 00:00:00.0002746, NetworkDuration: 00:00:00.0002338, SerializationDuration: 00:00:00.0000408
[2025-05-19 02:55:52.1768017][ConnectionReceivingMessageEvent]
[2025-05-19 02:55:52.1926554][ConnectionReceivedMessageEvent]Duration: 00:00:00.0157242, NetworkDuration: 00:00:00.0157039, DeserializationDuration: 00:00:00.0000203
[2025-05-19 02:55:52.1937283][ConnectionOpened] { ServerId : { ClusterId : 1, EndPoint : "Your EndPoint" }, LocalValue : 7, ServerValue : "46512" }
[2025-05-19 02:55:52.2014229][ConnectionSendingMessagesEvent]
[2025-05-19 02:55:52.2016386][ConnectionSentMessagesEvent]Duration: 00:00:00.0001328, NetworkDuration: 00:00:00.0000609, SerializationDuration: 00:00:00.0000719
[2025-05-19 02:55:52.2021239][ConnectionReceivingMessageEvent]
[2025-05-19 02:55:52.2179420][ConnectionReceivedMessageEvent]Duration: 00:00:00.0157738, NetworkDuration: 00:00:00.0152098, DeserializationDuration: 00:00:00.0005640
[2025-05-19 02:55:52.2373962][ConnectionSendingMessagesEvent]
[2025-05-19 02:55:52.2387203][ConnectionSentMessagesEvent]Duration: 00:00:00.0011985, NetworkDuration: 00:00:00.0000963, SerializationDuration: 00:00:00.0011022
[2025-05-19 02:55:52.2388917][ConnectionReceivingMessageEvent]
[2025-05-19 02:55:52.2606545][ConnectionReceivedMessageEvent]Duration: 00:00:00.0217241, NetworkDuration: 00:00:00.0216642, DeserializationDuration: 00:00:00.0000599
C# insert 100 documents: 44 ms
[2025-05-19 02:55:52.2723916][ConnectionSendingMessagesEvent]
[2025-05-19 02:55:52.2725729][ConnectionSentMessagesEvent]Duration: 00:00:00.0001225, NetworkDuration: 00:00:00.0000798, SerializationDuration: 00:00:00.0000427
[2025-05-19 02:55:52.2726212][ConnectionReceivingMessageEvent]
[2025-05-19 02:55:52.2892247][ConnectionReceivedMessageEvent]Duration: 00:00:00.0165636, NetworkDuration: 00:00:00.0164415, DeserializationDuration: 00:00:00.0001221
C# read 100 documents: 26 ms
[2025-05-19 02:55:52.2949230][ConnectionSendingMessagesEvent]
[2025-05-19 02:55:52.2952141][ConnectionSentMessagesEvent]Duration: 00:00:00.0002060, NetworkDuration: 00:00:00.0000525, SerializationDuration: 00:00:00.0001535
[2025-05-19 02:55:52.2952716][ConnectionReceivingMessageEvent]
[2025-05-19 02:55:52.3228256][ConnectionReceivedMessageEvent]Duration: 00:00:00.0275160, NetworkDuration: 00:00:00.0274847, DeserializationDuration: 00:00:00.0000313
C# delete 100 documents: 30 ms
Now, even with the data count increased to 1000, there is no longer an abnormally long execution time.
So the question should now be:
Why does this issue occur with the C# Driver on the Free Tier, but not with the Node.js Driver?
This behavior could easily discourage users who are testing with the C# Driver on the Free Tier and are unaware of this performance issue.
(I almost migrated the original server code to Node.js because of this issue… QAQ)