Are you finding the benefits and features of ZFS worth the perf penalty? Or maybe even its compression makes it overall a faster alternative to say ext4 for a database?
I’ve considered in the past running a DB in AWS with direct nvme drive used for SLOG and for L2ARC cache while the main storage would have been a mounted EBS volume, I haven’t tried it but am still wondering if it’s a better alternative to running a DB on top of bare EBS in Amazon (it should be a lot cheaper than say io2 type volume with provisioned IOPS)
If your dataset is small enough or you have plenty of resources, and you don’t need any fancy customizabilty and multitenancy (always searching only a subset of all documents, filtered by tenant ID) then Typesense.
Otherwise if Typesense can’t fit the index in your RAM it will not work, if you need to filter every search it will become slow.
If you need lots of customizability of how you index your documents and how you search, what you prioritize in the search, facets, nothing beats Elastic here. But it will need plenty of resources or otherwise it will be slow.
If you need fast but absolutely non customizable search that can live off a lot less than 1GB of RAM (less than 100MBs even) then you might have some success with https://github.com/valeriansaliou/sonic
If you’re constrained on resources but sonic is too limiting, then finally you might have some success with Manticore search. It’s featureful but using it with different languages can be a lot of work (I’m not sure why they don’t ship a distribution with all language plugins enabled and configured), the docs will be good enough to get you started. It can live off a few hundred MBs of RAM with large indexes, and will still be faster than Elastic.
ARM is cheaper on AWS per the unit of work done, in the general case. But there should be no assumption that ARM is that snappy little brother that will launch your lambdas in no time while x86 is still starting up, this is the kind of idea that I get when reading the comments mentioning ARM. It won’t launch your virtualized environment that noticeably faster. It’ll just do more work for less money, and 40% is probably not the figure that you’ll see in real life.
I don’t think that there’s motivation to optimize for the look of the end document that they write, they have to produce a lot of text, not a bunch of well formatted pages. A lot of people drive a car everyday but don’t know how to change oil for example.
I believe in GCC C a block can return a value. In this case it returns a pointer to __SCT__x86_pmu_add_tramp. And that pointer is then treated as a function.
My experience with Thinkpad P52 was quite bad. The intel graphics resets at least two times a day which requires a reboot to fix. I’ve filed an issue in the Intel DRM repository but haven’t got any answer yet, this might as well be a faulty hardware issue which I have to idea how to prove (Windows works fine and it’s all warranty would care about).
Plus it’s gigantic and heavy, its fingerprint sensor doesn’t have Linux drivers (there are some unofficial drivers that were implemented very recently but the laptop is a few years old at this point), the IR camera for face recognition doesn’t work either in Linux. It’s also noisy when it’s doing computationally expensive stuff, I’m not sure if there’s silent alternatives though.
It can support up to 64gb though and two NVMe drives + one Sata drive so that’s nice. But it drove me mad in the past few months that I’ve been using it, by hanging several times a day so I built instead a desktop machine for Linux as they never have these kind of issues, and for mobile use I might as well be fine with MBP from 2015
Consider that even at the highest tier you’ll max out at 20k IOPS and the speed on these cloud services doesn’t generally go beyond 200MB/s. Now you can google how much IOPS and read/write speed a typical nvme SSD will give you, maybe you’ll reconsider using RDS-like services then
I highly recommend ThoughtEmporium on YouTube btw. This guy literally does gene editing in his streams; not saying that he’s doing any breakthrough research but it’s at the very least inspiring and shows complex things in a very down to earth manner. See his videos on how he treated his lactose intolerance using a virus containing DNA that encodes lactase; or a recent video where he builds a plasmid DNA from genomes of Malaria + HIV for treating cancer developing antibodies against cancer and letting immune system do the hard work (might sound silly with all those HIV and malaria but there’s some actual research behind that)
Looks like the methods are already there but they’re not streamlined yet, as well as the research. You’d most likely go for an existing virus that targets cell mitochondria specifically, maybe you’d want mitochondria of a specific cell. The viral DNA can be altered in the ways you want and the virus can deliver the DNA to your cells. I’m not sure how specifically this would be done, usually they use viruses to deliver a small portion of a DNA that encodes a specific protein, so the main objective there is to make the cell produce that protein. Not sure how that would work with simply mortifying existing DNA.
My personal experience was that neither Firefox’s pioneering alternative to what Chrome announces here (tab groups), nor tree style tab extension were convenient enough to use. With tab groups you obviously very quickly neglect trying to group newly created tabs and even if you, it’s not very helpful (except for sand boxing - that’s a nice thing to have). Tree style tabs were just a pain in the ass, it was constantly causing my tabs to jump around when I opened them, it seems like it was trying to reorder my tabs in the horizontal tab bar so that the ordering would mimic the tree leaves while the vertical tab bar was just useless to me, maybe simply because I could not get used this layout.
I ended up using stash tab extension, as I often have to concentrate on researching one specific thing and while I do that I don’t need any other unrelated tabs to be open, this allows me to retroactiavely group all opened tabs into different stacks and name each of them and then just stash them away like you’d do with git stash, they don’t take up any memory after that and I can return to the entire stash at some point by clicking a single button that will effectively do a git pop of the stash.
This doesn’t seem to touch the subject of Promgen (or other Prometheus configuration management software that I’m not aware of). Configuring it via yaml files, especially the alerts in alert manager and queries in the sql exporter, requires more steps than I’d like to do. Any recommendations on how to manage Prometheus configs? Especially having multiple Prometheus instances where the master node scraps all the data from other nodes
Last time we tried to use it there were real problems with date filtering in SQL based DBs and it’s a must for big datasets that span over time (this looks like the most common use case to me). Basically metabase would generate WHERE condition that would like `date(date_column) BETWEEN ... AND ...` (or if you were filtering by minutes or years this would be something else). This prevents DB from being able to use an index on date_column and don’t even get me started on why adding indexes for all sorts of `date(...)`, `year(...)` etc expressions is not an optimal solution. I ended up fixing this in metabase and opened a PR https://github.com/metabase/metabase/pull/9860
Which was initially welcomed but then was ignored for a few months (we were using our forked version in my company in the meantime), after which was closed because they’ve fixed it differently and sure enough they did and it was a neater fix architecture-wise. Just that it didn’t actually fix the majority of use cases so there’s now new isssue opened with the same problem described
https://github.com/metabase/metabase/issues/11502
And surely it’s ignored. Since then we migrated to a relatively simpler Redash, we’ve found that none of the people at our company who were supposed to benefit from GUI query builder never actually used it and only engineers were building dashboards, and for us it’s obviously easier to write SQL. One benefit of Redash I’ve noticed was that it allows you to schedule dashboard queries to run for example every 10 minutes which means that amount of users of the dashboard doesn’t add any load to the DB because they get cached results and those results are relatively fresh at the same time.
Maybe you could open source it, and with the help of people from the community get sort of grant from Google or Amazon or say digital ocean so that this could work without you having to pay for servers? All the work that contractors were doing, people could do that for free. The only thing is I’d license this thing so that it can’t be used commercially (except for research)
If you’re talking about scopes of variables then if language supports it, the best of both worlds would be to have an inlined version where each block has its own scope so that you can easily track which variables are actually shared among those scopes and which only belong to certain scopes.
All sorts of market inequalities including when developers cut corners can be fixed by proper regulation and oversight. At the end of the day the cooperatives of people who want to build a few-story home together and they hire a managing company that will direct the building but they will be able to oversee the books should be the winning strategy imo. It just takes more involment from each tenant during construction but ultimately that’s the only way you can be sure that something is done the way you want it - oversee it yourself. It is a burden obviously but given the stakes I think it’s justifiable.
It might not give you an answer but nevertheless quite interesting and might be enlightening to you, there’s a podcast called The History of Oil, it covers Venezuela among other countries.
If we are talking languages of certain paradigms imposing discipline then JS not being a language conceived or further developed with FP in mind is not one of those, regardless of how folks use it.
The reason to use PHP over JS/Python or Ruby is that PHP supports strict typing and that makes code both more maintainable, understandable (Find Usage feature only works reliably when types are inferrable which is not always the case in those other theee langs) and refactorable.
Now the reason to use PHP over Java or Go is that PHP at this point has a type system that’s on par with Go’s but at the same time it gives you an advantage of fast development process thanks to the lack of need for compilation and/or restarting the container after each change in the code. I’m currently working with Java and before that I had a long experience of PHP, while I personally would choose Java over PHP almost in any case because I value type system features perhaps a bit too much, but I do suffer from those slow turnaround times (compile/restart TomCat) and I can see how it could potentially be bad for the business at early stages especially.
So the bottom line is PHP at this point has a nice balance which is hard to find atm in any other popular languages with evolved ecosystem
The first one is basically the messaging system and a smart broker. I’m not aware of any brokers that would take into account how busy a particular node (they usually just use round robin approach) but surely the concept you outlined is far from being a definition of over-engineering, cron is almost always worse because it is hardly scalable (it is with some crutches and until some point when it becomes unscalabel again, and it introduces a consistent delay).
I understood it as he compared last modified of two files that were downloaded consecutively. Now if you take the difference between those last modified dates that would be the time spent downloading one of these files (which one is up to which date was greater). That is assuming that files were being copied synchronously one by one (like cp would do)
If only they decided that their awesome email client should live in a browser again. I still use Opera 12 solely for emails as their new dedicated email client was lacking a large number of features in comparison.