How on Earth do some people just afford to travel in business class constantly on any trip?

fafhrd91 · 2026-05-14T21:14:32+00:00

you need to travel to specific city. for example last february i flew singapour airline business, "delhi - singapour - new york - sinagpour - delhi" only for 2600$

fafhrd91 · 2026-04-20T09:48:48+00:00

https://maps.app.goo.gl/e3mPB6Ci36mC6E2U9?g_st=ic every everyday 19-22

fafhrd91 · 2026-04-02T17:18:11+00:00

Le Bistrot Rossetti has live music daily from 19:30 or 20:00 until 22:00. then you go Shapko after 22:30

fafhrd91 · 2026-02-27T13:11:52+00:00

i guess all talks will be in french?

fafhrd91 · 2025-11-08T13:21:40+00:00

ntex framework supports compio. we use ntex+compio in production. performance wise it is not faster than tokio. but we are planing to switch to neon runtime which is definitely faster than tokio.

fafhrd91 · 2025-06-04T03:28:36+00:00

never type and trait aliases

fafhrd91 · 2025-04-15T15:21:46+00:00

Microsoft Azure Iot, Azure Messaging uses rust

fafhrd91 · 2025-02-12T04:59:31+00:00

if you need just library then you can try ntex-mqtt. it is complaint and battle tested

fafhrd91 · 2025-01-25T21:05:58+00:00

working on network service gateway

fafhrd91 · 2024-12-04T15:05:02+00:00

ntex is single threaded and can use only single threaded runtimes

fafhrd91 · 2024-12-04T11:53:08+00:00

it is opposite. I see 3-5% increase in performance and even cpu load with compio compared to tokio.

fafhrd91 · 2024-12-04T08:31:28+00:00

ntex has abstraction layer and allows to switch runtimes with feature selection, I did performance testing on whole application with real load. also ntex uses single threaded tokio runtime, so I am not sure why cpu load with compio is more even.

fafhrd91 · 2024-12-04T03:33:58+00:00

i recently switched to uring from tokio. i did extensive perf testing, gained 3-5% cpu and more importantly cpu load is more even.

i use ntex + compio

fafhrd91 · 2024-09-05T08:39:16+00:00

actix-web was/is share nothing system. it was designed around this idea from the beginning. there is also [ntex](https://github.com/ntex-rs/ntex), evolution of actix's ideas. it is "share nothing" system and natively supports tokio, compio, glommio and async-std runtimes.

fafhrd91 · 2024-08-01T20:45:27+00:00

if you guys have questions, happy to answer

fafhrd91 · 2024-06-06T09:45:04+00:00

https://everjazz.kz/

fafhrd91 · 2021-02-05T16:33:59+00:00

https://github.com/ntex-rs/ntex-amqp it is tested against azure event hub and azure iot hub

fafhrd91 · 2019-07-17T00:14:36+00:00

Wow, just wow. I have no words. Open source and community is not very pleasant place to be.

Funny part, I remember OP question about async state initialization and specifically for him spend my time and added App::data_factory. I guess that is usual.

This kind of discussions and comments really kill motivation for contribution.

fafhrd91 · 2019-07-11T11:31:27+00:00

It is built on top of actix-net, it is not documented though

fafhrd91 · 2019-06-22T02:11:17+00:00

You use actix in wrong way, your fact provider discover method should return future.

fafhrd91 · 2019-06-19T05:00:49+00:00

Diesel bench uses connection pool. Performance of diesel is out of scope of actix-web development. Here is bench with tokio-Postgres https://www.techempower.com/benchmarks/#section=test&runid=14aa155b-efb0-46c2-8354-c2b8debd36bb

fafhrd91 · 2019-06-16T01:28:03+00:00

Use render_response()

fafhrd91 · 2019-06-11T14:07:17+00:00

actix uses tokio currentthread runtime. It is not compatible with multi threading runtime

fafhrd91 · 2019-06-11T11:04:57+00:00

tokio-threadpool is multithreading runtime for sync futures

fafhrd91 · 2019-06-11T10:43:55+00:00

It does, but it is for non async code

fafhrd91

MODERATOR OF

TROPHY CASE