You have experienced otcl compile failures when you install all-in-one package to your mac. (Like this : Undefined symbols for architecture x86_64) I find a way to install ns-2.35 version to mac OS (Lion 64bit). You needs tcl8.5.11, tk8.5.11, tclcl-1.20, otcl-1.14, and ns-2.35. You can get files via "http://www.isi.edu/nsnam/ns/ns-build.html" I assume that your folder locate in /Users/kwangjo/Documents/ns Open terminal and goto the folder. ! You should install Xcode before doing follow instruction. 1. Change superuser mode sudo su tar xvfz "PACKAGES" 2. compile tcl8.5.11 cd /Users/kwangjo/Documents/ns/tcl8.5.11 cd unix ./configure --enable-framework --enable-64bit make make test ## you should pass all test. make install 3. compile tk8.5.11 cd /Users/kwangjo/Documents/ns/tk8.5.11 ./configure --enable-framework --enable-64bit make make install 4. compile otcl-1.14 ! Before compile, you should make library link and include link. l...
Running local LLMs on two P104-100 GPUs EXPERIMENT NOTEBOOK · 2026-10-18 Running local LLMs on two P104-100 GPUs From environment setup to Qwen and Strata performance and coding tests 0. Summary Two 8GB P104-100 GPUs ran local LLMs successfully. Qwen Q2 led in generation speed; Strata Coder passed the most tasks among the local configurations in this coding evaluation. Median coding generation was 31.42 tok/s for Q2 and 11.45 tok/s for Coder. Q2 passed two of six custom coding tasks, while Coder passed four. Test Main result Interpretation Build and startup Two P104 GPUs; CUDA 12.4 / sm_61 build succeeded; Qwen and Strata returned responses Both engines ran on this hardware. Synthetic prompt / decode Q2 layer: 543.77 / 31.87 tok/s; Q4 layer: 9.89 / 20.68 tok/s Q2 was faster. Q4 included CPU offloading, so quantization was not the only variable. Context Q2 32K: 27.47 tok/s; Q4 4K: 20.54 tok/s (three decode runs each) Synthetic decoding was confirmed, not accura...
Android M adds powerful battery managing modes. One is doze and the other is app stand by. Today google Korea campus, there is conference about these two modes. I write summary about the conference meeting. Mr yang and many other company people are participated in. Because M source code is not released yet, we just talk and sharing testing results about these two modes. So following question (other company people) and answer (Mr yang from google) may have wrong informations. So, testing your application using adb commend. Some pending events will occurs malfunction to your applications. Q&A 1. What is doze mode? - Doze mode aim is for saving battery when user does not move their device for a long time. For example, if user forget to charging the phone, and slept. The phone turn to doze mode until wake up at the morning. In the doze mode, whole app does not working at all. (some hardware interrupt and google play service can working even it is doze mode.) ...
댓글
댓글 쓰기