docker stop $(docker ps -a -q)
docker rm $(docker ps -a -q)
docker rmi $(docker images -q)
docker rm $(docker ps -a -q)
docker rmi $(docker images -q)
fix the Meta/Alt/Option key in iTerm
iTerm2 > Preferences > Profiles > Keys > Change Option key to "Esc+"
iTerm2 > Preferences > Profiles > Keys > Change Option key to "Esc+"
/usr/bin/perf_4.9 record --call-graph dwarf,65528 -F 99 -p "10811,10812,10813,10814,10815,10816,10817,10818,10819,10820,10821,10822,10823,10824,10825,10826,10827,10828,10829,10830,10831,11261,11416"
Последнее время достаточно часто можно увидеть сайты подобные https://shopomio.ru/
из выдачи
https://shopsy.ru/
https://likewear.ru/
https://www.glami.ru/
https://shopliga.ru/
https://lookbuck.com/
https://fashion-me.ru
https://likenilook.ru/
логика у всех одна, каталог с категориями/брендами/фильтрами - при переходе на товар редиректит на озон/юкс/купивип и т.д.
может есть готовый движок под это или иное решение?
трафа там прилично, пример https://lookbuck.com/
Total Visits (Russia Aug 2019) — 460315
http://joxi.ru/L21pYJZFRqB63m
практически у всех сеошка
из выдачи
https://shopsy.ru/
https://likewear.ru/
https://www.glami.ru/
https://shopliga.ru/
https://lookbuck.com/
https://fashion-me.ru
https://likenilook.ru/
логика у всех одна, каталог с категориями/брендами/фильтрами - при переходе на товар редиректит на озон/юкс/купивип и т.д.
может есть готовый движок под это или иное решение?
трафа там прилично, пример https://lookbuck.com/
Total Visits (Russia Aug 2019) — 460315
http://joxi.ru/L21pYJZFRqB63m
практически у всех сеошка
shopomio.ru
ShopoMio - интернет-магазин одежды и обуви. Купить брендовые товары по скидкам с доставкой по Москве, СПБ и России
В интернет моле ShopoMio собрана лучшая одежда и обувь со всего мира по привлекательной цене с доставкой по России
*UPSERT OPTIMIZE*
I noticed/tested that is much faster for INSERTS (have yet to test UPSERTS) to use a WHERE NOT EXISTS in addition to ON CONFLICT. Typically about 3x faster than just allowing the ON CONFLICT to handle existence checks. I think this may carry over into UPSERTS, making it likely faster to do an INSERT and then and UPDATE. Here is my test for inserts only...
--so i can keep rerunning
DROP TABLE if exists temp1;
DROP TABLE if exists temp2;
--create a billion rows
SELECT GENERATE_SERIES AS id INTO TEMP temp1
FROM GENERATE_SERIES(1, 10000000);
CREATE UNIQUE INDEX ux_id ON temp1(id);
ALTER TABLE temp1 CLUSTER ON ux_id;
--create a second table to insert from, with the same data
SELECT * INTO TEMP temp2
FROM temp1;
CREATE UNIQUE INDEX ux_id2 ON temp2(id);
ALTER TABLE temp2 CLUSTER ON ux_id2;
--test inserting with on conflict only
INSERT INTO temp1(id)
SELECT id
FROM temp2 ON conflict DO nothing;
--execution time: 14.71s (1million rows)
--test inserting with not exists and on conflict
INSERT INTO temp1(id)
SELECT t2.id
FROM temp2 t2
WHERE NOT EXISTS (SELECT 1 FROM temp1 t1 WHERE t2.id = t1.id)
ON conflict DO nothing;
--execution time: 5.78s (1million rows)
I noticed/tested that is much faster for INSERTS (have yet to test UPSERTS) to use a WHERE NOT EXISTS in addition to ON CONFLICT. Typically about 3x faster than just allowing the ON CONFLICT to handle existence checks. I think this may carry over into UPSERTS, making it likely faster to do an INSERT and then and UPDATE. Here is my test for inserts only...
--so i can keep rerunning
DROP TABLE if exists temp1;
DROP TABLE if exists temp2;
--create a billion rows
SELECT GENERATE_SERIES AS id INTO TEMP temp1
FROM GENERATE_SERIES(1, 10000000);
CREATE UNIQUE INDEX ux_id ON temp1(id);
ALTER TABLE temp1 CLUSTER ON ux_id;
--create a second table to insert from, with the same data
SELECT * INTO TEMP temp2
FROM temp1;
CREATE UNIQUE INDEX ux_id2 ON temp2(id);
ALTER TABLE temp2 CLUSTER ON ux_id2;
--test inserting with on conflict only
INSERT INTO temp1(id)
SELECT id
FROM temp2 ON conflict DO nothing;
--execution time: 14.71s (1million rows)
--test inserting with not exists and on conflict
INSERT INTO temp1(id)
SELECT t2.id
FROM temp2 t2
WHERE NOT EXISTS (SELECT 1 FROM temp1 t1 WHERE t2.id = t1.id)
ON conflict DO nothing;
--execution time: 5.78s (1million rows)