1,700 karma · joined January 9, 2021
If you just use a pre-built package, the AGPL has the exact same requirements as the GPL.
- max_concurrent_queries, since each query uses a certain amount of memory
- max_memory_usage, which is the max per-query memory usage
Here's my full config for running clickhouse on a 2GiB server without OOMs. Some stuff in here is likely irrelevant, but it's a starting point.
diff --git a/clickhouse-config.xml b/clickhouse-config.xml
index f8213b65..7d7459cb 100644
--- a/clickhouse-config.xml
+++ b/clickhouse-config.xml
@@ -197,7 +197,7 @@
<!-- <listen_backlog>4096</listen_backlog> -->
- <max_connections>4096</max_connections>
+ <max_connections>2000</max_connections>
<!-- For 'Connection: keep-alive' in HTTP 1.1 -->
<keep_alive_timeout>3</keep_alive_timeout>
@@ -270,7 +270,7 @@
-->
<!-- Maximum number of concurrent queries. -->
- <max_concurrent_queries>100</max_concurrent_queries>
+ <max_concurrent_queries>4</max_concurrent_queries>
<!-- Maximum memory usage (resident set size) for server process.
Zero value or unset means default. Default is "max_server_memory_usage_to_ram_ratio" of available physical RAM.
@@ -335,7 +335,7 @@
In bytes. Cache is single for server. Memory is allocated only on demand.
You should not lower this value.
-->
- <mark_cache_size>5368709120</mark_cache_size>
+ <mark_cache_size>805306368</mark_cache_size>
<!-- If you enable the `min_bytes_to_use_mmap_io` setting,
@@ -981,11 +980,11 @@
</distributed_ddl>
<!-- Settings to fine tune MergeTree tables. See documentation in source code, in MergeTreeSettings.h -->
- <!--
<merge_tree>
- <max_suspicious_broken_parts>5</max_suspicious_broken_parts>
+ <merge_max_block_size>2048</merge_max_block_size>
+ <max_bytes_to_merge_at_max_space_in_pool>1073741824</max_bytes_to_merge_at_max_space_in_pool>
+ <number_of_free_entries_in_pool_to_lower_max_size_of_merge>0</number_of_free_entries_in_pool_to_lower_max_size_of_merge>
</merge_tree>
- -->
<!-- Protection from accidental DROP.
If size of a MergeTree table is greater than max_table_size_to_drop (in bytes) than table could not be dropped with any DROP query.
diff --git a/clickhouse-users.xml b/clickhouse-users.xml
index f1856207..bbd4ced6 100644
--- a/clickhouse-users.xml
+++ b/clickhouse-users.xml
@@ -7,7 +7,12 @@
<!-- Default settings. -->
<default>
<!-- Maximum memory usage for processing single query, in bytes. -->
- <max_memory_usage>10000000000</max_memory_usage>
+ <max_memory_usage>536870912</max_memory_usage>
+
+ <queue_max_wait_ms>1000</queue_max_wait_ms>
+ <max_execution_time>30</max_execution_time>
+ <background_pool_size>4</background_pool_size>
+
<!-- How to choose between replicas during distributed query processing.
random - choose random replica from set of replicas with minimum number of errors- toaster oven on
- rice cooker on
- both on
- both off
I would be extremely surprised if the sense was able to detect a rice cooker accurately.
But you keep reading just a little bit, and you find out this company is a victim of a leveraged buyout:
> The family management team … departing in 2013 The deal — which valued 99 Cents Only Stores at $1.6 billion — saddled the company with a debt load that turned a “conservative balance sheet” into a “highly leveraged capital structure,”
This is absolutely shameless. The owners put the company on incredibly shaky footing, then when a bump in the road comes up, they use it to do politics and refuse to take responsibility?
This process is called subrogation and it is out of the control of the injured person.
The Emporia Vue is half the price and has a clamp for each circuit.
In this case though, the wall plug monitoring is definitely the right solution.
> Note: GitHub automatically includes two archives Source code (zip) and Source code (tar.gz) in the releases. These archives cannot be disabled and should be ignored.
The author was thinking ahead! Latest commit hash for this repo: 8a3b5f28d00ebc2c1619c87a8c8975718f12e271
> Every Discourse Discussion returns data in JSON if you append .json to the URL.
then this:
> Raw data was gathered into a single JSONL file by automating a browser using Playwright.
Kinda seems to me like having a whole browser instance for this isn't necessary? I would have been surprised if this .json pattern didn't continue for all pages, and it turns out that it does in fact also work for the topic list: https://community.openai.com/latest.json
The other place I've seen this sort of API pattern is reddit. For example, https://www.reddit.com/r/all.json or (randomly chosen) https://www.reddit.com/r/mildlyinfuriating/comments/1bqn3c0/...
I'm not going to argue too much with this, but I think this is underselling Ikea quite a bit.
Their cheap stuff is definitely made out of cheap materials. But I've found it to be well-engineered compared to walmart with reinforcements in critical places and general overall good quality control (doesn't come pre-scratched).
Walmart-level furniture on the other hand is often designed to look a certain way, with no consideration for how loads will be placed on it or long-term durability.
Or do you mean that existing owner should be required to get their neighbors' consent to do what they want with their own property?
Anyone selling their home would, all other things being equal, prefer to sell their home to an neighbor with which they have a relationship then to a random person. The neighbors should make an offer if they really care.
I'd much rather get information from an individual or small group who is intrinsically motivated and is not just looking for the lowest bar of quality that won't make folks immediately bounce.
I also want to note that just putting Google Analytics on there doesn't kill the site's ranking. There are some sites that are just infested, and those are what get dramatically downranked.
function requestIsBad(request) {
return [
/Do Anything Now/i,
/[A-Z]{4+}/,
/10 tokens/i,
].some(regex => regex.test(input));
}
it's a good time to be selling shovels!or through WASM: https://github.com/electric-sql/pglite
1. align the image stack. not trivial, but a common task.
2. take several cross-sections, in both dimensions, and have a human draw a line along a specific layer line
3. linearly interpolate these lines into a surface.
4. for each pixel in each output layer, set the value to layers[l + offset][x][y], where the offset was calculated in step 3.
Might another way to resolve issues with the PCB dishing be to photograph the layers at a fraction of a layer height? So that in that way you have a lot more slices to work with, and you can digitally "flatten" the PCB?
Or are you maybe aware of other images of depopulated boards?
It doesn't seem like this problem requires anything crazy, just traditional computer vision, but of course the devil is in the details.
1. zuck's perfect pacing and word choice
2. the friend pulling up browser windows perfectly on-cue, and zuck pointing at exactly the right place
3. second camera already set up to capture the friend
Meanwhile my ESPHome devices have never had any issue whatsoever.