ãƒ¡ãƒ¢å¿…é ˆï¼æ–™ç†å®¶ãŒãƒ˜ãƒ“ãƒãƒ†ã§ä½œã‚‹ã€Œãƒã‚®ãã†ã‚ã‚“ã€ãŒå¤§ãƒã‚ºã‚Šã€Œ3回ã¯ãƒªãƒ”ートã™ã‚‹ã§ã—ょã€ï¼ˆCHANTO WEB） - Yahoo!ニュース
ã“ã‚Œã‹ã‚‰ã®å£ç¯€ã€é£Ÿå“ã«ç™»å ´ã™ã‚‹æ©Ÿä¼šã‚‚増ãˆãã†ãªãã†ã‚ん。料ç†å®¶ã®misaã•ã‚“ãŒInstagramã«æŠ•ç¨¿ã—ãŸã€Œãƒã‚®ãã†ã‚ã‚“ã€ãŒè©±é¡Œã§ã™ã€‚ ã€ç”»åƒã€‘ã“ã‚Œã¯çµ¶å“ï¼350万人ã«è¦‹ã‚‰ã‚ŒãŸå¤§ãƒã‚ºã‚Šã®ã€Œãƒã‚®ãã†ã‚ã‚“ã€ã®ä½œã‚Šæ–¹ï¼ˆå…¨8枚） ■昨年巷ã§ãƒã‚ºã£ãŸã€Œãƒã‚®ãã†ã‚ã‚“ã€ã‚’ 昨年Instagramãªã©SNSã§ãƒã‚ºã£ã¦ã„ãŸã¨ã„ã†ã€Œãƒã‚®ãã†ã‚ã‚“ã€ã€‚misaã•ã‚“ã‚‚ã€å½“時ã‹ã‚‰ã‚ˆã作ã£ã¦ã„ã¦ã€å‹äººãŒæ¥ãŸã¨ãã«ãŠã‚‚ã¦ãªã—æ–™ç†ã¨ã—ã¦å‡ºã™ã¨ã€Œç¾Žå‘³ã—ã„ï¼ã©ã†ã‚„ã£ã¦ä½œã‚‹ã®ï¼Ÿã€ã¨å¿…ãšä½œã‚Šæ–¹ã‚’èžã‹ã‚ŒãŸãã†ã€‚ãã“ã§ã€è‡ªåˆ†ã®ãƒ¬ã‚·ãƒ”を「3回ã¯ãƒªãƒ”ートã™ã‚‹ã§ã—ょã€ã¨ã„ã†æ–‡è¨€ã¨ã¨ã‚‚ã«Instagramã«æŠ•ç¨¿ã—ãŸã®ã ãã†ã€‚ フォãƒãƒ¯ãƒ¼ãŸã¡ã‹ã‚‰ã¯ã€Œç§ã‚‚3回作ã£ãŸã€‚ã¾ã‚“ã¾ã¨ã€ã€Œã‚ã£ã¡ã‚ƒãƒãƒžã£ã¦10回以上リピートã—ã¦ã‚‹ã€‚ã¨ã„ã†ã‹æ™®é€šã®ãã†ã‚ん食ã¹ãªããªã£ãŸã€ã€Œå†™çœŸæ’®ã‚‹å‰ã«ãªããªã£ã¦ã‚‚ーãŸã€‚。。腰抜ã‹ã—ã¾ã—ãŸã€ãªã©ã®å£°ãŒå¯„ã›ã‚‰ã‚Œã€ã™ã£ã‹ã‚Šãã®æ‰‹è»½ã•
サクッã¨å§‹ã‚るプãƒãƒ³ãƒ—トエンジニアリングã€LangChain / ChatGPT】
ã“ã®æœ¬ã§ã¯ã€åˆå¿ƒè€…・入門者ã®æ–¹ã«å‘ã‘ã¦ã€ãƒ—ãƒãƒ³ãƒ—トエンジニアリングã®çŸ¥è˜ã‚„使ã„方を体系的ã«ã¾ã¨ã‚ã¾ã—ãŸã€‚ ã€æ¦‚è¦ã€‘ ・内容：プãƒãƒ³ãƒ—トエンジニアã¨ã¯ï¼Ÿã€ãƒ—ãƒãƒ³ãƒ—トエンジニアã®å¿…é ˆã‚¹ã‚ル5é¸ã€ãƒ—ãƒãƒ³ãƒ—トデザイン入門ã€è³ªå•ãƒ†ã‚¯ãƒ‹ãƒƒã‚¯10é¸ã€‘ã€LangChainã®æ¦‚è¦ã¨ä½¿ã„æ–¹ã€LangChainã®ã‚¤ãƒ³ã‚¹ãƒˆãƒ¼ãƒ«æ–¹æ³•ã€Python】ã€LangChainã®ã‚¤ãƒ³ã‚¹ãƒˆãƒ¼ãƒ«æ–¹æ³•ã€JavaScript・TypeScript】ã€LCEL（LangChain Expression Language）ã®æ¦‚è¦ã¨ä½¿ã„æ–¹ã€LangSmithã®æ¦‚è¦ã¨ä½¿ã„æ–¹ã€LLMOps】ã€LangServeã®æ¦‚è¦ã¨ä½¿ã„æ–¹ã€API】ã€LangGraphã®æ¦‚è¦ã¨ä½¿ã„æ–¹ã€Multi-Actor】ã€OpenGPTsã®æ¦‚è¦ã¨ä½¿ã„æ–¹ã€OSS版ã®GPTs】ã€LangChain Evaluationsã€ç”Ÿæˆç‰©ã®è©•ä¾¡æ–¹æ³•ã€‘ã€LangChain Hubã€Op
Azure Application Gateway ã§ã® WebSocket ã®ã‚µãƒãƒ¼ãƒˆ
Application Gateway ã§ã¯ã€ã‚らゆるè¦æ¨¡ã®ã‚²ãƒ¼ãƒˆã‚¦ã‚§ã‚¤ã§ WebSocket ãŒãƒã‚¤ãƒ†ã‚£ãƒ–ã«ã‚µãƒãƒ¼ãƒˆã•ã‚Œã¾ã™ã€‚ ユーザーãŒæ§‹æˆå¯èƒ½ãªã€WebSocket ã®ã‚µãƒãƒ¼ãƒˆã‚’é¸æŠžçš„ã«æœ‰åŠ¹ã¾ãŸã¯ç„¡åŠ¹ã«ã™ã‚‹ãŸã‚ã®è¨å®šã¯ã‚ã‚Šã¾ã›ã‚“。 RFC6455 ã§æ¨™æº–化ã•ã‚ŒãŸ WebSocket プãƒãƒˆã‚³ãƒ«ã¯ã€é•·æ™‚é–“ã«åŠã¶ TCP 接続上ã§ã‚µãƒ¼ãƒãƒ¼ã¨ã‚¯ãƒ©ã‚¤ã‚¢ãƒ³ãƒˆé–“ã®å…¨äºŒé‡é€šä¿¡ã‚’å¯èƒ½ã«ã—ã¾ã™ã€‚ ã“ã®æ©Ÿèƒ½ã«ã‚ˆã‚Šã€HTTP ベースã®å®Ÿè£…ã§ã¯å¿…é ˆã ã£ãŸãƒãƒ¼ãƒªãƒ³ã‚°ã‚’使用ã™ã‚‹ã“ã¨ãªãã€Web サーãƒãƒ¼ã¨ã‚¯ãƒ©ã‚¤ã‚¢ãƒ³ãƒˆã®é–“ã«ã‚ˆã‚Šå¯¾è©±çš„ãªåŒæ–¹å‘通信ãŒå¯èƒ½ã«ãªã‚Šã¾ã™ã€‚ WebSocket ã¯ã€HTTP ã¨ã¯ç•°ãªã£ã¦ã‚ªãƒ¼ãƒãƒ¼ãƒ˜ãƒƒãƒ‰ãŒå°‘ãªãã€è¤‡æ•°ã®è¦æ±‚ã‚„å¿œç”ã§åŒã˜ TCP 接続をå†åˆ©ç”¨ã§ãã‚‹ãŸã‚ã€ãƒªã‚½ãƒ¼ã‚¹ã‚’より効率的ã«ä½¿ç”¨ã§ãã¾ã™ã€‚ WebSocket プãƒãƒˆã‚³ãƒ«ã¯ã€å¾“æ¥ã® HTTP ãƒãƒ¼ãƒˆ 80 ãŠã‚ˆã³ 443 上ã§å‹•
WebSocket サーãƒãƒ¼ã‚’ ECS(Fargate) ã§æ§‹ç¯‰ã—ã¦ã¿ãŸ | DevelopersIO
WebSocket を使ã£ã¦åŒæ–¹å‘通信をã™ã‚‹ã“ã¨ãŒã§ãるサーãƒãƒ¼ã‚’ ECS(Fargate) 㨠ALB を使ã£ã¦æ§‹ç¯‰ã—ã¦ã¿ã¾ã™ã€‚サーãƒãƒ¼ã¯ã€ Node.js ã® ws を使ã£ã¦å®Ÿè£…ã—ã¾ã™ã€‚より安全ãªé€šä¿¡ã‚’ã™ã‚‹ãŸã‚ã« wss を利用ã—ã¦é€šä¿¡ã—ãŸã„ã®ã§ã€è¨¼æ˜Žæ›¸ã¯ AWS Certificate Manager(ACM) を使用ã—ã¦ä½œæˆã—ã¾ã™ã€‚ 構築ã™ã‚‹æ§‹æˆã®ã‚¤ãƒ¡ãƒ¼ã‚¸ã¯ã€ä»¥ä¸‹ã¨ãªã‚Šã¾ã™ã€‚ 動作環境 Node.js: v16.15.1 ws: 8.11.0 ECR ã«ãƒªãƒã‚¸ãƒˆãƒªã‚’ä½œæˆ ã‚³ãƒ³ãƒ†ãƒŠãƒ¬ã‚¸ã‚¹ãƒˆãƒªã¨ã—㦠ECR を利用ã™ã‚‹ãŸã‚ã€ãƒªãƒã‚¸ãƒˆãƒªã‚’作æˆã—ã¾ã™ã€‚今回ã¯ãƒ†ã‚¹ãƒˆç”¨ã§ã™ãŒã€ãƒ—ライベートãªãƒªãƒã‚¸ãƒˆãƒªã¨ã—ã¦ã„ã¾ã™ã€‚ リãƒã‚¸ãƒˆãƒªä½œæˆå¾Œã€ãƒ—ッシュコマンドã®è¡¨ç¤º をクリックã™ã‚‹ã¨ã€ã‚³ãƒ³ãƒ†ãƒŠã®ãƒ“ルドã‹ã‚‰ãƒ—ッシュã¾ã§ã®ã‚³ãƒžãƒ³ãƒ‰ã‚’確èªã™ã‚‹ã“ã¨ãŒã§ãã‚‹ã®ã§ã€ã‚³ãƒžãƒ³ãƒ‰ã‚’å‚考ã«ã‚¤ãƒ¡ãƒ¼ã‚¸ã‚’プッシュã—ã¾ã™ã€‚ Web
Using multiple nodes | Socket.IO
This is documentation for Socket.IO 3.x, which is no longer actively maintained. When deploying multiple Socket.IO servers, there are two things to take care of: enabling sticky session, if HTTP long-polling is enabled (which is the default): see belowusing the Redis adapter (or another compatible Adapter): see belowSticky load balancing​If you plan to distribute the load of connections among diff
大é‡æŽ¥ç¶šã«è€ãˆã‚‹WebSocketアプリケーションサーãƒæ§‹ç¯‰ã®ã‚³ãƒ„ - pixiv inside [archive]
WebSocketã®æ‰±ã†ã‚µãƒ¼ãƒ“スã§ã¯ã€é•·æ™‚é–“ã®ã‚³ãƒã‚¯ã‚·ãƒ§ãƒ³ã€å†æŽ¥ç¶šå‡¦ç†ã€ãƒ—ãƒã‚ã‚·ã€ãƒãƒ¼ãƒ‰ãƒãƒ©ãƒ³ã‚µãªã©ã€ã‚¤ãƒ³ãƒ•ãƒ©ã®é¢ã§å¤šãã®å•é¡Œã‚’抱ãˆãŒã¡ã§ã™ã€‚弊社ã®ã‚µãƒ¼ãƒ“ス「pixivã€ã®9周年ä¼ç”»ã§ã‚‚ã€ã“ã®å•é¡Œã«ç›´é¢ã—ã¾ã—ãŸã€‚ 実際ã«ãã“ã§æ§‹ç¯‰ã—ãŸã‚¤ãƒ³ãƒ•ãƒ©ã®äº‹ä¾‹ã‚’ã‚‚ã¨ã«ã€æœ¬é‹ç”¨ã«ä½¿ãˆã‚‹WebSocketサーãƒã®æ§‹æˆã«ã¤ã„ã¦ã€pixivインフラ部ã®å—å·ã‹ã‚‰ã”紹介ã—ã¾ã™ã€‚ * 9周年ä¼ç”» “黒æ´å²â€ã‚’ãƒã‚±ãƒƒãƒˆã§å®‡å®™ã«é£›ã°ã™ pixivé»’æ´å² ãã‚‚ãã‚‚ WebSocket ã¨ã¯ï¼Ÿ WebSocketã¯TCP上ã§å‹•ãåŒæ–¹å‘通信ã®ãŸã‚ã®é€šä¿¡è¦æ ¼ã§ã™ã€‚ Webページã®èªã¿è¾¼ã¿ã§è¡Œã‚ã‚Œã¦ã„るよã†ãªã€ã‚¯ãƒ©ã‚¤ã‚¢ãƒ³ãƒˆãŒã‚µãƒ¼ãƒã«ãƒ‡ãƒ¼ã‚¿ã‚’è¦æ±‚ã—ã€ã‚µãƒ¼ãƒã¯ã‚¯ãƒ©ã‚¤ã‚¢ãƒ³ãƒˆã«ãƒ¬ã‚¹ãƒãƒ³ã‚¹ã‚’è¿”ã™ã¨ã„ã†HTTPã®é€šä¿¡ãƒ«ãƒ¼ãƒ«ã¨ã¯é•ã„ã¾ã™ã€‚サーãƒã¨é•·æ™‚間コãƒã‚¯ã‚·ãƒ§ãƒ³ã‚’確立ã—ã€Socketã®ã‚ˆã†ã«ãƒ‡ãƒ¼ã‚¿ã®ã‚„ã‚Šå–ã‚Šã‚’è¡Œã„ã¾ã™ã€‚ãã—ã¦ã€ã‚³ãƒã‚¯ã‚·ãƒ§ãƒ³ã‚’
![大é‡æŽ¥ç¶šã«è€ãˆã‚‹WebSocketアプリケーションサーãƒæ§‹ç¯‰ã®ã‚³ãƒ„ - pixiv inside [archive]](https://cdn-ak-scissors.b.st-hatena.com/image/square/6c57cca624676cf40b39e3e1415d2dfc953a0caa/height=288;version=1;width=512/https%3A%2F%2Fcdn.image.st-hatena.com%2Fimage%2Fscale%2F7dacfc8cda4e58f1ca88281fb302b5a46633ad99%2Fbackend%3Dimagemagick%3Bversion%3D1%3Bwidth%3D1300%2Fhttps%253A%252F%252Fcdn-ak.f.st-hatena.com%252Fimages%252Ffotolife%252Fd%252Fdevpixiv%252F20161129%252F20161129204837.png)
Module ngx_http_upstream_module
Defines the address and other parameters of a server. The address can be specified as a domain name or IP address, with an optional port, or as a UNIX-domain socket path specified after the “unix:†prefix. If a port is not specified, the port 80 is used. A domain name that resolves to several IP addresses defines multiple servers at once. The following parameters can be defined: weight=number sets
Nginxを用ã„ãŸWebSocketサーãƒã®ReverseProxy構æˆåŠã³SSL/TLS接続 - tail my trail
TL;DR 今更ãªãŒã‚‰ã€éšåˆ†å‰ã®ä½œæ¥ãƒ¡ãƒ¢ãŒè²¯ã¾ã£ã¦ã„ãŸã®ã¨ã€ã‚‚ã†ä¸€ã¤ã®è¨˜äº‹ã®ã¤ãªãŽã¨ã™ã‚‹ãŸã‚ã«åã出ã—ã¦ãŠã。 WebSocket 通信ã®SSL/TLS通信をã•ã›ãŸã‚Šãƒãƒ¼ãƒ‰ãƒãƒ©ãƒ³ã‚·ãƒ³ã‚°ã•ã›ãŸã„å ´åˆãªã©ã€WebSocketサーãƒã®å‰æ®µã«ReverseProxyã‚’ç½®ããŸã„時㯠Nginx (v1.3.13 以é™) を使ãŠã†ã¨ã„ã†è©±ã€‚ ãªãŠã€AWSã®ELB (ALB: Application Load Balancer) を使ã£ã¦ã‚‚実ç¾ã§ãるよã†ã«ãªã£ãŸã®ã§ã€AWSã§é‹ç”¨ã—ã¦ã„るサービスã®å ´åˆã¯ALB使ã£ãŸã»ã†ãŒãŠæ‰‹è»½çœã‚³ã‚¹ãƒˆãƒ¡ãƒªãƒƒãƒˆå¤§ãã„ã¨æ€ã†ã€‚ ã¯ã˜ã‚㫠以å‰Node.js 自身ã§SSL/TLS通信ã™ã‚‹æ–¹æ³•ã‚’記ã—ãŸãŒã€ シングルコアã§å‹•ä½œã™ã‚‹Node.jsプãƒã‚»ã‚¹ã«ã€æš—å·åŒ–ã®ã‚ªãƒ¼ãƒãƒ¼ãƒ˜ãƒƒãƒ‰ã¾ã§é£Ÿã‚ã›ã‚‹ã®ã¯éžå¸¸ã«ã‚‚ã£ãŸã„ãªã„。 pm2ãªã©ã®Node.js製ã®ã‚¯ãƒ©ã‚¹ã‚¿ãƒªãƒ³ã‚°ãƒ„ールã§ãƒžãƒ«ãƒãƒ—ãƒã‚»ã‚¹
streamlitã®ä»•çµ„ã¿èª¿æŸ» - Qiita
pythonã§æ‰‹è»½ã«Webアプリケーションを作れるフレームワークstreamlitã®ä»•çµ„ã¿ã«ã¤ã„ã¦èª¿ã¹ã¦ã¿ã¾ã—ãŸã€‚（誤解ãŒã‚ã‚Šã¾ã—ãŸã‚‰ã€ã©ã†ãžã”指摘ãã ã•ã„。） 周辺ã®æ¥å‹™ã§ä½¿ã†ã“ã¨ãŒçµæ§‹å¢—ãˆã¦æ¥ãŸãŸã‚ã€ä½•ã‹æ€§èƒ½ã§å•é¡Œã«ãªã£ãŸå ´åˆã‚„æ‹¡å¼µãŒå¿…è¦ãªå ´åˆã«ã‚‚対応出æ¥ã‚‹ã‚ˆã†ã«ã¨èª¿ã¹ã¦ã¾ã¨ã‚ã¾ã—ãŸã€‚ githubã®ã‚³ãƒ¼ãƒ‰ã¨å…¬å¼ã®ãƒ‰ã‚ュメントをå‚考ã«èª¿æŸ»ã—ã¦ã„ã¾ã™ã€‚ https://github.com/streamlit/streamlit アーã‚テクãƒãƒ£ streamlit 㯠Python(tornade)+React(typescript)ã§å®Ÿè£…ã•ã‚Œã¦ã„ã¾ã™ã€‚ streamlitã§ã¯ã€æ¬¡ã®2ã¤ã®ãƒ‘ートãŒã‚ã‚Šã¾ã™ã€‚ web server : streamlitã®pythonアプリケーションコードをブラウザã«è¡¨ç¤ºã™ã‚‹ãŸã‚ã®ãƒ•ãƒãƒ³ãƒˆã‚¨ãƒ³ãƒ‰ã®HTML+jsをインスタンス化ã—ã¦é€šä¿¡ã™ã‚‹ãŸã‚ã«ä½¿ç”¨ã—ã¾ã™ã€‚
How Nvidia’s CUDA Monopoly In Machine Learning Is Breaking – OpenAI Triton And PyTorch 2.0
How Nvidia’s CUDA Monopoly In Machine Learning Is Breaking – OpenAI Triton And PyTorch 2.0 Over the last decade, the landscape of machine learning software development has undergone significant changes. Many frameworks have come and gone, but most have relied heavily on leveraging Nvidia’s CUDA and performed best on Nvidia GPUs. However, with the arrival of PyTorch 2.0 and OpenAI’s Triton, Nvidia’
リリースã€éšœå®³æƒ…å ±ãªã©ã®ã‚µãƒ¼ãƒ“スã®ãŠçŸ¥ã‚‰ã›
最新ã®äººæ°—エントリーã®é…ä¿¡
j次ã®ãƒ–ックマーク
kå‰ã®ãƒ–ックマーク
lã‚ã¨ã§èªã‚€
eコメント一覧を開ã
oページを開ã
» IBMã€ã‚¤ãƒ³ãƒ†ãƒ«ã¨Nvidiaã‚’æ載ã—ãŸã‚¯ãƒ©ã‚¦ãƒ‰AIスーパーコンピュータ「Velaã€ã‚’発表
WebSocket support in Azure Application Gateway
NGINX+ and Highly Available WebSockets in an Auto-Scaling AWS Environment | SolvIT Inc.
Scalable WebSocket Architecture
nginx websocket consistant hashing loadbalancing based on part of url path
nginx-websocket-proxy/load-balancing.conf at master · nicokaiser/nginx-websocket-proxy
{{#tags}}- {{label}}
{{/tags}}