dennisgorelik: (Default)
ElasticSearch team defends the bloat in ElasticSearch Percolator 5.4
--------
https://github.com/elastic/elasticsearch/issues/25308
If you're not interested in ranking you can easily turn it off, by wrapping the percolate query in a constant_score query.
.....
The percolator tries to tag the queries automatically based on the containing query terms. However it can't do this for all percolator queries, because the percolator doesn't know how to extract meaningful information during indexing for all queries. This is a work in progress and will get better over time. It already has shown a significant performance improvement for cases where the percolator was able to analyze the percolator query correctly at index time.
--------

1) Funny how in order to turn off unneeded feature, application developers have to create an extra wrapper around their query.

2) "work in progress" did not stop ElasticSearch team from breaking backward compatibility and forcing their users to rewrite their legacy code in favor of "work in progress" ElasticSearch 5.4.

3) "a significant performance improvement" is not quantified, and the cases where that improvement happened -
not described.

See also: ElasticSearch Percolator Bloat - part 1
dennisgorelik: (Default)
I bought NUC7i3BNH.
Then I tried to install Windows Server 2016 Standard on that NUC.
Windows Server installation itself was successful, but several drivers, including Network Adapters(!) and "Multimedia Audio Controller" - did not install.

Search for drivers brought me to:
http://www.intel.com/content/www/us/en/support/boards-and-kits/intel-nuc-boards/000005628.html
where to my amazement I discovered that most of NUCs do NOT support Windows Server OS.

Further research pointed me to a hack that allows to manually use Windows 10 drivers on Windows Server 2016.
It goes like this:
1) Open C:\install\LAN_Server2016_64_22\PRO1000\Winx64\NDIS65\e1d65x64.inf
2) From this section:
[Intel.NTamd64.10.0.1]

copy these 3 lines:
===
%E15D8NC.DeviceDesc% = E15D8.10.0.1, PCI\VEN_8086&DEV_15D8
%E15D8NC.DeviceDesc% = E15D8.10.0.1, PCI\VEN_8086&DEV_15D8&SUBSYS_00008086
%E15D8NC.DeviceDesc% = E15D8.10.0.1, PCI\VEN_8086&DEV_15D8&SUBSYS_00011179
===

into this section:
[Intel.NTamd64.10.0]

3) Then turn off drivers checks:
bcdedit /set LOADOPTIONS DISABLE_INTEGRITY_CHECKS
bcdedit /set TESTSIGNING OFF
bcdedit /set NOINTEGRITYCHECKS ON

4) And finally install the driver:
pnputil.exe -i -a C:\install\LAN_Server2016_64_22\PRO1000\Winx64\NDIS65\e1d65x64.inf

After that Network (and Internet) started working on my new NUC.


But I do not understand - why Intel does not allow these drivers under Windows Server 2016 by default?

Update: Windows Server 2016 on NUC7i3BNH struggles - part 2.
dennisgorelik: (Default)
By juan-gandhi:
---
1) Мутабельные ключи в "хашмапе".
2) Стек для регистрации данных для последующей проверки, что мусора не осталось. Т.к. указатель на стек глобальный, а бегают несколько ниток, то чистый абсурд.
3) Класс на 183 метода, 0 тестов.
4) Регулярно, случайным образом, рушащиеся тесты, и святая вера, что "за последние несколько лет у нас ничего не ломалось".
5) Вера в то, что у нас все очень "эффективно" - и регулярные жалобы юзеров, что наш код очень медленный, в отличие от скального конкурента (!)
6) "Оптимистический мерж" - "это не мой тест упал, я тут не при чем, нам нужно релизить.
---

1) Интересно, зачем кому-то понадобилось делать мутабельные ключи в хашмапе?
2) Мне лично не встечалось, хотя при работе в multithread environment каких только ляпов не сделаешь...
3), 4), 5), 6) - мне в том или ином виде встречалось.
dennisgorelik: (2009)
Lots of applications need to load and convert document files of different formats into other formats or into text.
You would have think that there would be a good solution to it.
Unfortunately it's not the case.
Existing solutions are either for desktop only, or buggy or extremely expensive (~$10K/year).

I thought I found a solution - DevExpress Document Server library for $599.99

Unfortunately, after running for couple of weeks it crashed my service with StackOverflowException exception:
----
https://www.devexpress.com/Support/Center/Question/Details/T257097
To my regret, there is no simple workaround to avoid this exception with your document. Regarding the time frame for fixing this issue, it is difficult to provide any estimate in such cases.
----

So now I need to find a way to prevent my service from dying in case if some random document is fed into it.

Sigh.

Profile

dennisgorelik: (Default)
Dennis Gorelik

July 2017

S M T W T F S
      1
2345678
9 101112 131415
16171819202122
23242526272829
3031     

Syndicate

RSS Atom

Most Popular Tags

Style Credit

Expand Cut Tags

No cut tags
Page generated Jul. 20th, 2017 12:33 pm
Powered by Dreamwidth Studios