Skip to main content

Fitness inspektor: World Class Wenceslas/Vaclavské náměstí

By
Druhou zastávkou na tour de multisport karta bylo fitko na Václaváku, konkrétně World Class Wenceslas. Hned na začátku, kvůli lokaci, trošku problém s parkováním, protože na Václavském náměstí člověk prostě zdarma nezaparkuje.

Zařízení má vlastně tři podlaží. Nahoře recepce, pár strojů, v mezipatře cardio a sál, dole klasická posilka včetně regulérní hrazdy - asi jediné plus, které jsme ještě ke všemu nepoužili :-) V pátek večer narváno zrovna nebylo, ale fitko vypadalo plné, nedokážu si představit třeba úterý večer.

Všechna patra jsou v podzemí, takže žádná okna. Díky tomu na mě nepůsobilo nijak pozitivním dojmem. Když člověk přičte starší stroje, tak z návštěvy nadšený moc nejsem. Sprchy, šatny a sauna celkově horší, takže za me tři mínus.
Labels:

Comments

Post a Comment

Popular posts from this blog

Performance Battle of NoSQL blob storages #1: Cassandra

By
Preface We spend last five years on HP Service Virtualization using MsSQL database . Non-clustered server. Our app utilizes this system for all kinds of persistence. No polyglot so far. As we tuned the performance of the response time - we started at 700ms/call and we achieved couple milliseconds per call at the end when DB involved - we had to learn a lot of stuff. Transactions, lock escalation , isolation levels , clustered and non clustered indexes, buffered reading, index structure and it's persistence, GUID ids in clustered indexes , bulk importing , omit slow joins, sparse indexes, and so on. We also rewrite part of NHibernate to support multiple tables for one entity type which allows use scaling up without lock escalation. It was good time. The end also showed us that famous Oracle has half of our favorite features once we decided to support this database. Well, as I'm thinking about all issues which we encountered during the development, unpredictive behavio
3 comments
Read more

ETCD: POST vs. PUT understanding

By
ETCD is distributed key value store used as a core component in CoreOS . I've already send a post earlier this week. Here is a page describing how to use ETCD basic commands = ETCD API. Code snippets placed in a page mostly use put , but ETCD allows to use post as well.  Most of us understand differences between those two commands in a notion of a REST(ful) service, but how does it work in key value store? POST Example over many words. curl -v http://127.0.0.1:2379/v2/keys/test -XPOST -D value="some value" curl -v http://127.0.0.1:2379/v2/keys/test -XPOST -D value="some value" Two same command result into following content: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 { "action" : "get" , "node" : { "key" : "/test" , "dir" : true , "nodes" : [ { "key" : "/test/194" , "value" : &
2 comments
Read more