To optimize your file transfer speed between PC and NAS, I create a BFNP to help you do a quick check in your network. BFNP is Background process, File type, Network, and Protocol.
Maybe that’s why the SSD write test on TS-112 and TS119PII are slower than traditional hard drive. Need to enable trim in QNAP. For Linux kernel 2.6.33, trim is disabled by default.
Indeed if a SSD doesn’t trim, then every write to a previously written block must first be read, erased, modified, and re-written to the same location thus crippling write performance.
Since I have run quite some benchmark tests, and massively copied large files such .vmdk and .iso files and deleted them all afterward, the write performance got lower and lower.
My TS-459 runs a Linux QNAPNAS02 126.96.36.199 which does support natively TRIM function but I was sad to learn that while it’s available, it is not used at all because it is inadequate for today’s real TRIM hardware. This is not a QNAP problem but an issue with the Linux kernel developers. In the interim Mark Lord, who’s by the way one…
View original post 819 more words
What happen when you choose a more powerful processor for your NAS? What’s the different if I choose two-bay over one-bay device?
NAS are not as flexible as personal computers on spec. Most will provide fix spec on processor and bay. Some have RAM upgrades as options on certain models. Therefore, performance questions are difficult to tell.
It is interested to see mobile development move focus from consumer to business customers. For business apps, integration with existing service, data modeling, business rules, workflow, SDLM are important. I am interested in this platform.
This a very comprehensive short post on SoC. I have working on porting ZurmoCRM onto QNAP TS-119PII which has a Marvell 2.0GHz. My initial test is very depressed on the performance: 104 seconds for two records. I expect to see performance improvements on Armada XP or need to move to Atom x86 platform for acceptable performance.
The acronym “SoC” generally refers to “System on a Chip”. But with SoCs entering the server space, it is also taking on a new meaning: “Server on a Chip”. An SoC is a large scale integration of processor cores, memory controllers, on-chip and off-chip memories, peripheral controllers, accelerators, and custom IP (intellectual property) for specific applications and uses. As Moore’s law continues, chip process geometries shrink, allowing more transistors to reside on the same area of silicon. Traditionally, server processors have used this new real estate to add more cores. But there are better alternatives than just adding more cores for certain applications.
Increasing integration in an SoC brings a number of benefits including:
- Higher performance – significantly faster and wider internal busses compared to those found in a multi-chip or multi-board solution.
- Lower power – wider range of power optimization techniques can be employed in SoCs including power gating, changing…
View original post 536 more words