Loading...

XML

Word

Printable

JSON

Type: Task
Resolution: Done
Priority: Major - P3
Fix Version/s: None
Affects Version/s: None
Component/s: None
Labels:
- egress-grpc-perf
- init-539-public-preview

Assigned Teams:

Networking & Observability
Backwards Compatibility:
Fully Compatible
Sprint:
Networking & Obs 2025-01-20, Egress gRPC 2025-02-14, N&O 2025-03-17
Story Points:
2
Confidence Status:
None
Work Order:
3

Aha! Reference:
None
Tracking Level:
None
Risk Status:
None
Exec Notes:
None
Goal Name:
None
Goal Link:
None

Run e2e performance tests testing mongod/mongot search communication using gRPC, and confirm whether or not the results meet the scope goals:

Do not introduce more than 5ms of additional latency for search operations when this feature is enabled and authentication is disabled, as measured by the M30-replset-AWS-S20_2-ARM64-mdb-rapid - concurrent.query.text-with-limit-10 benchmark.

See the design for more details.

depends on

SERVER-97153 Implement asyncConnect function in gRPC

Closed

SERVER-97155 Change Search TaskExecutors to use gRPC

Closed

SERVER-97158 Add singleUseConnections flag to ConnectionPool::Options

Closed

SERVER-98254 Revisit lock contention in GRPCClient

Backlog

SERVER-99666 Don't start gRPC default egress reactor until it is needed

Backlog

is related to

SERVER-97663 Generate initial MongoRPC performance numbers for M30-replset-AWS-S20_2-ARM64-mdb-rapid - concurrent.query.text-with-limit-10 Performance Test

Closed

(1 is related to)

Assignee:: Erin McNulty
Reporter:: Erin McNulty
Participants:: Erin McNulty
Votes:: 0 Vote for this issue
Watchers:: 2 Start watching this issue

Created:: Nov 14 2024 04:45:42 PM UTC
Updated:: Mar 11 2025 09:40:06 PM UTC
Resolved:: Mar 11 2025 09:40:06 PM UTC
Confidence Status Last Update:: 06/Mar/25 6:29 PM

Details

Description

Attachments

Issue Links

Activity

People

Dates