You’ve finished your manuscript (or nearly finished it!) and you’re ready to get some quotes for book design and printing. But first you’ll want to know approximately how many pages your finished book will have. Here’s a simple way to calculate your book’s approximate page count using the word count of your manuscript. Istat menus 6 20.
Find your word count In Word, click anywhere in your document and your word count will show in the status bar at the bottom left, between the number of pages and the dictionary language.
Choose a trim size You’ll need to choose a trim size for your book just as a starting point, so choose the one below that’s the most appropriate for your book:
ADRP 6-0 provides a starting point for the exercise of mission command. It establishes how commanders, supported by their staffs, apply the foundational mission command philosophy with the mission command warfighting function to lead forces toward mission accomplishment. The doctrine in this publication is a guide. FM 6-0, 5 May 2014, is changed as follows: Remove Old Pages Insert New Pages front cover front cover pages i through vi pages i through vi pages 7-1 through 7-2 pages 7-1 through 7-2 pages 9-23 through 9-45 pages 9-23 through 9-46 pages B-1 through B-7 pages B-1 through B-7.
For fiction: 5.5″ x 8.5″ For nonfiction: 6″ x 9″
Large format books with illustrations are more difficult to predict the final page count, but usually large pages will have a similar amount of text as small pages, as part of the large page will be devoted to illustrations, sidebars, captions, and so on. Choose one of the above sizes, even for your large format book, just as a starting point.
Calculate the number of pages Using your current word count and the appropriate formula below, calculate the number of pages you can expect in your finished book:
Your word count divided by 390 = page count for a 5.5″ x 8.5″ book For example: 50,000 divided by 390 = 128.20 pages
Your word count divided by 475 = page count for a 6″ x 9″ book For example: 50,000 divided by 475 = 105.26 pages
As you can see, a smaller trim size will produce more pages for the same word count, and a larger trim size will produce less. These formulas are based on using:
a standard typeface for book publishing (Garamond)
a standard type size (11 pt)
standard margins
standard spacing (the first line of each paragraph is indented, and there are no blank lines between paragraphs)
Calculate the number of pages for front and back matter Don’t forget to add to your page count a title page, copyright page, table of contents, appendix, index, and any other pages that are not included in your manuscript but will form part of your published book.
I also add an extra half page for each chapter, because each chapter opens slightly down from the top margin, and seldom ends at the bottom of the last page.
Calculate the number of pages your images will require Will you be adding images to your pages? If so, the number and size of your images will affect your page count. Here’s an easy way to calculate how many extra pages your images will require:
count your images and divide them into rough sizes: full page, half page and quarter page
calculate the number of pages based on these figures. For example: 5 images @ 1 page = 5 pages 20 images @ 0.5 page = 10 pages 20 images @ 0.25 page = 5 pages
And finally, calculate the approximate number of pages in your upcoming book! Add together the number of pages from your:
word count
front and back matter
images
Voila!
Knowing your approximate page count can be helpful in a number of situations. You can start obtaining quotes for printing, calculating costs of shipping, and choosing a price for your book, well in advance of having your book designed.
Controlling your page count You may be surprised by your page count, and realize that your book is going to be thinner or thicker than you anticipated. Moving to even a slightly larger page size can lower your page count and save printing costs. Or, if your book is slimmer than you’d hoped, you can choose a smaller page size, a larger font size, and a paragraph style which adds more generous spacing (and more pages) to your book.
This type of information is very helpful to your book designer. If your book needs to be thicker to improve perceived value, your book designer can help in many ways. Similarly, if your book is lengthy and you want to keep printing and shipping costs down, your book designer can minimize your page count by creating a design with this in mind.
Thanks for making it through this lengthy post. I hope it’s helpful!
Page 60
Transparent page sharing (TPS) is a mechanism where the vmkernel automatically identifies identical pages of virtual memory and consolidates them to a single physical memory page, in a manner that is transparent to the virtual machine guest operating system. In vSphere 6, intra-VM TPS is enabled by default and inter-VM TPS is disabled by default, due to some security concerns as described in VMware KB 2080735. You can change the TPS behavior by applying the salting mechanism as described in VMware KB 2097593. A low priority, scheduled vmkernel process uses a hashing mechanism to apply TPS by identifying matching pages within a virtual machine and other processes, depending on TPS settings. Naturally, the amount of page sharing depends on factors such as the amount of matching pages among the virtual machines and other worlds. The amount of memory pages claimed by inter-VM TPS, when enabled, can rise as the number of virtual machines running the same guest OS rises. This number is negatively impacted by the use of large pages (2 MB pages). Most modern guest operating systems use large pages, which cannot be shared by the vmkernel. Page sharing is not a direct sign of memory contention, since it may be engaged regardless of the memory state; however, in the Clear memory state, the TPS service is actively called instead of waiting on the next scheduled TPS run. Also in the High memory state, the ESXi host begins breaking large memory pages into small pages, which facilitates an increase in page sharing.
In vSphere 5.x, TPS could be considered as an indirect sign of memory contention, since it tends to only engage significantly when the ESXi host is experiencing memory pressure. Per VMware KB 2080735, VMware disabled inter-VM page sharing by default in updates for VMware 5.x.
You can set a virtual machine’s advanced parameter sched.mem.pshare.salt to control its ability to participate in transparent page sharing. TPS is only allowed within a virtual machine (intra-VM TPS) by default, because the ESXi host configuration option Mem.ShareForceSalting is set to 2, the sched.mem.pshare.salt is not present in the virtual machine configuration file, and thus the virtual machine salt value is set to unique value. In this case, to allow TPS among a specific set of virtual machines, set the sched.mem.pshare.salt of each virtual machine in the set to an identical value. Alternatively, to enable TPS among all virtual machines (inter-VM TPS), you can set Mem.ShareForceSalting to 0, which causes sched.mem.pshare.salt to be ignored and to have no impact. Or, to enable inter-VM TPS as the default, but yet allow the use of sched.mem.pshare.salt to control the effect of TPS per virtual machine, set the value of Mem.ShareForceSalting to 1. In this case, change the value of sched.mem.pshare.salt per virtual machine to prevent it from sharing with all virtual machines and restrict it to sharing with those that have an identical setting.
in ESXi 6.0, the five memory states are High, Clear, Soft, Hard, and Low, where Clear is a new state in version 6.0. The states are based on a value called minFree, which is 899 MB for the first 28 GB of ESXi host memory plus 1% of any additional host memory. For example, for a 100GB ESXi host, minFree is 899 MB plus 1% of (100 GB – 28GB) = 1619 MB. The thresholds for each state is based on the amount of free available memory in the host compared to the minFree value. The thresholds are High equals 400% minFree, Clear equals 100% minFree, Soft equals 64% minFree, Hard equals 32%, and Low equals 16%. When the free ESXi host memory drops below 400% minFree (the High threshold), ESXi begins breaking large pages into small pages. At the Clear threshold, TPS is actively called, instead of waiting for next TPS run. At the Soft threshold, ballooning begins. At the Hard threshold, compression and swapping begins. At the Low threshold, blocking begins, where certain virtual machines are prevented from allocating memory.
Page 60 Big Book
The main impact of the Clear threshold is that you should expect to see increased page sharing activity well before you see ballooning. Ballooning will not engage until the Soft threshold (64%) is crossed, but page sharing may engage at any time, and will actively engage as the Clear threshold (100%) is crossed.
In the vSphere Web Client performance graphs, the Memory – Shared metric can be used to monitor the size in kilobytes (KB) of the amount of memory that is shared by TPS, which reduces the need to engage memory ballooning, compression or swapping.