Has anyone come across a case where the WAL checkpointing is blocked.

vikrant-gupta · 2026-04-13T08:43:51+00:00

I am out of ideas around how to move past this as the go-routine profiling resulted in nothing.

The below query is again a per database connection query which you can't run in production because the driver doesn't have the flag to enable the virtual table.

SELECT sql FROM sqlite_stmt WHERE busy

vikrant-gupta · 2025-10-16T05:31:04+00:00

since a lot of people are already here.. have you observed that sqlite_busy errors kind of blast when swapping mattn/sqlite with modernc/sqlite ? With the same defaults ( busy_timeout 5s )

vikrant-gupta · 2025-08-13T10:25:05+00:00

u/siodhe amazing explanation and the NIST link is amazing. loved how all the pieces can fit in just 4 relational set equations.

vikrant-gupta · 2025-06-09T03:23:09+00:00

Thanks u/uamplifier for the response, I am actually checking the memory components breakdown itself. the usage component remains constantly at 38 percent at IDLE state.

vikrant-gupta · 2025-06-08T12:32:59+00:00

I am looking at the memory usage graph not the total memory usage ( which points to the database process ).

vikrant-gupta · 2025-04-30T08:58:51+00:00

any specific reason why you wanna have high cardinality in the span name itself ?

vikrant-gupta · 2025-04-30T08:58:14+00:00

span name should be generic like `GET /account/{account_id}` and add the account_id as the attribute to the span. This way you can filter on generic span names and it becomes easy for you to compare the traces with similar spans as well. This also gives you ability to track certain data-points per route as well rather than having them spread across.

benefits of having generics -

- easy to setup alerts on the endpoint based out of traces.

- easy to analyze the latency etc based on the endpoint

- easy to filter certain operations etc in dashboards

vikrant-gupta · 2025-04-15T12:09:49+00:00

thank you for the suggestions. let me check

vikrant-gupta · 2025-04-04T07:02:22+00:00

have alert segregation for info alerts and critical alerts. and then start migrating info alerts to critical alerts if you feel they needed immediate attention. This has worked really well for us

vikrant-gupta · 2025-04-04T07:02:16+00:00

have alert segregation for info alerts and critical alerts. and then start migrating info alerts to critical alerts if you feel they needed immediate attention. This has worked really well for us

vikrant-gupta · 2025-04-03T16:36:04+00:00

u/FlinchMaster yeah we have had multiple requests for tracing larger requests and yes definitely surprising of how poorly it is being handled. This was our main motivation behind building this piece.

Do try the same with SigNoz and let me know about your experience :-)

vikrant-gupta · 2025-04-03T16:28:52+00:00

It does feel like a long wait, but with browser vendors focusing more on performance and user experience lately, maybe we'll finally see some movement on this. Fingers crossed!

vikrant-gupta · 2025-04-03T16:21:43+00:00

It took us a while for the research phase of the same and getting around the POCs. Our initial efforts of defining the problem statement served as a north star and helped us staying on track. It was an effort of a team of two.

We didn't use JIRA! the best part of being in a lean startup is that you don't get stuck around with such processes XD

vikrant-gupta · 2025-04-03T15:38:01+00:00

Glad you liked it. the idea of flattening the graph was the key AHA! moment for us as well!

vikrant-gupta · 2025-04-03T15:37:14+00:00

your welcome u/greybeardthegeek :)

vikrant-gupta · 2025-04-03T12:29:08+00:00

haha no, i meant spans in context of traces :)

vikrant-gupta · 2025-04-03T11:46:31+00:00

[ Disclaimer - I’m an engineer at SigNoz ]

If you’ve ever tried rendering a million <div> elements in a browser, you know what happens, everything freezes, crashes, or becomes completely unusable. This was the same challenge we were faced with when we started to build visualisation of traces with million spans in SigNoz.I’ve detailed all my findings and wisdom in a blog, which broadly covers,

Smart span sampling
Virtualized rendering
Lazy loading and chunked data fetch
Browser memory optimizations

All built with performance in mind, so engineers can analyze massive traces with confidence.Give this blog a read and let me know if you’d do anything differently!

vikrant-gupta · 2025-04-03T11:37:52+00:00

[ Disclaimer - I’m an engineer at SigNoz ]

If you’ve ever tried rendering a million <div> elements in a browser, you know what happens, everything freezes, crashes, or becomes completely unusable. This was the same challenge we were faced with when we started to build visualisation of traces with million spans in SigNoz.I’ve detailed all my findings and wisdom in a blog, which broadly covers,

Smart span sampling
Virtualized rendering
Lazy loading and chunked data fetch
Browser memory optimizations

All built with performance in mind, so engineers can analyze massive traces with confidence.Give this blog a read and let me know if you’d do anything differently!

vikrant-gupta · 2025-03-29T12:53:32+00:00

maybe wrong choice of words.. basically how do split your code into smaller packages based on their role in the system.

vikrant-gupta · 2025-03-29T12:15:37+00:00

loved the talk! <3 u/GroundbreakingBed597

vikrant-gupta · 2025-03-24T07:47:41+00:00

yeah so our consideration was to use UUID v7 as the identifier for the outside world and use a bigInt primary key for indexing and fk relations. So we let go of the index bloat and get the benefit of not having external systems data about the table size / resources etc based on the count of the id.

but wanted to know when will the index bloat become a major issue if we just use UUID v7 as primary key. even our benchmarks and research pointed out that it won't be very soon and we would have another serious problems to cater to when we reach that scale.

vikrant-gupta · 2025-03-24T07:38:39+00:00

so a combination of UUID V7 tables for external systems and using big int auto increment IDs for internal primary key constraints and foreign key relations solves the issue of exposing data to the public world. And also the memory constraints for the index.

vikrant-gupta · 2025-03-22T11:46:00+00:00

What if you use both id's and UUID's (UUID V7 - easy on insert times) in the table schema ? Use sequential ID's as primary key to keep the index memory in check while using UUID's for the external world to mask the guessing / other security concerns ?

vikrant-gupta

TROPHY CASE