itroot
Joined 12 years ago
Joined 12 years ago
I'm not political or activist of any kind. However sometimes it makes sense to get understanding how other people think, so sometimes I read comments here and there.
HN has its own bias as well. Usually the quality of discussion here is quite high though.
Also do not miss twitter and facebook. Youtube is working (so far) with no ads.
Also stuff like WaPo is perfectly acessible. Sometimes I skim through it (also mostly comments), then check ZeroHedge to get the opposite view.
So a lot of info is acessible. Quite a few of resources are blocked on the other side though.
I surely can use VPN but prefer not to unless that required for more intellectual activity then reading news.
I have experience in mentorship, and now I'm mentoring a FE guy who wants to move into go development. It very interesting and fulfilling to help another person to achieve theirs goals.
* network access - do you have data that will be accessed frequently, and with high traffic? You need to cover this skewed access pattern in your solution.
* data migration from one node to another, etc...
* ability to restore quickly in case of failure.
I would suggest to:
* use some open-source solution on top of the hosted infrastructure (Hetzner or similar is a good choice)
* bring in a seasoned expert to analyze your data usage/storage patterns, maybe there are some other ways to make storage more cost effective, that simply moving out of AWS S3.
First, I wish Alexey fast recovery.
Second, Alexey wasn't a popular politic figure in past time, I believe that his peak of popularity was in 2013-2015.
Third, I think no one here is actually benefiting from this tragic event... the whole story just seems quite strange. Frankly, there a lot of more simple approaches that can kill a man - no need to use sophisticated things like chemical weapons (which actually doesn't work as intended).
I hope that this story will be more clear pretty soon.
It's perfectly ok to write to sqlite from different processes in the same time, but to achieve good results it's better to:
* use WAL mode - so the readers and writers do not block (you can turn on it with `PRAGMA journal_mode=WAL;` in CLI, and it's better to add `PRAGMA main.synchronous=NORMAL;` also).
* all concurrent writes will be queued by sqlite3 lib and done in sequential manner, and if any write attempt will wait longer that BUSY_TIMEOUT ( see https://www.sqlite.org/pragma.html#pragma_busy_timeout ) , it will return error.
Snippet
# setting things up...
itroot@l7490:/tmp$ grep -i pragma ~/.sqliterc
PRAGMA journal_mode=WAL;
PRAGMA main.synchronous=NORMAL;
PRAGMA busy_timeout=1000;
itroot@l7490:/tmp$ sqlite3 test.sqlite 'CREATE TABLE records (id INTEGER PRIMARY KEY, record TEXT);' > /dev/null 2>&1
# running 10 parallel processes that inserts numbers from 1 to 1000...
itroot@l7490:/tmp$ echo {1..1000} | xargs -n1 -d' ' -P 10 -i% sqlite3 test.sqlite 'INSERT INTO records (record) VALUES (%);' >/dev/null 2>&1
# getting number of records
itroot@l7490:/tmp$ sqlite3 test.sqlite 'SELECT count(*) FROM records;'
count(*) = 1000