dr_strangelove

4 ms·

1.
AI is starting to Rule the Battlefield(phillipspobrien.substack.com)
8 points by dr_strangelove 3y ago|3 comments
2.
by dr_strangelove 3y ago
The architecture is described here: https://youtu.be/Xa_fNuaSE_I?t=416
3.
by dr_strangelove 16y ago
For german users a similar service is offered by 1&1 (iPayment, with "silent CGI"-mode). The form on the site is sent to the ipayement servers and those verify the transaction data, call a URL on your servers with the unique transaction
4.
by dr_strangelove 16y ago
To open a terminal simply press cmd + return.
5.
by dr_strangelove 17y ago
if you had an index on device_id there shouldn't be a difference in performance between the original table and the partioned one. the index is used to reduce the rows that need to be scanned so there wouldn't be a full table scan. btw, why
6.
by dr_strangelove 17y ago
had this guy an index on "device_id" and "date_added", there is no way such a query would take 3-4 seconds.
7.
by dr_strangelove 17y ago
To give you a background why vacuum is necessary: When you update a row in postgres, it is marked as deleted and a row with the updated contents is inserted. Likewise, when you delete a row, it is only marked as deleted but the space on dis
8.
by dr_strangelove 17y ago
You don't need VACUUM FULL. If you have problems with too much disk space used by your tables, increase the autovacuum frequency.
9.
by dr_strangelove 18y ago
The language that fits this description best is Erlang, I would say ... (what, in this definition, is specific to objects compared to processes?)