Using hugepages (Large Pages)

I am trying to leverage this feature in TimesTen v7.0.5 running SUSE Linux v 2.6.5-7.244-smp (gcc version 3.3.3) but with no success.
I enabled hugepages in Linux:
vm.nr_hugepages=1024
vm.disable_cap_mlock=1
cat /proc/meminfo shows:
HugePages_Total: 1024
HugePages_Free: 1024
Hugepagesize: 2048 kB
I followed the instructions and set -linuxLargePageAlignment in the daemon options file (ttendaemon.options):
-linuxLargePageAlignment 2
However when I start TimesTen, first the daemon and then manual load the database in Ram, I did not see it use any hugepages. cat /proc/meminfo still shows HugePages_Free: 1024.
I also set /etc/security/limits.conf file properly. However, it differs with documentation is that I did not set /proc/sys/vm/hugetlb_shm_group since I have a older Linux kernel that hasn't support this param. Instead, I set vm.disable_cap_mlock = 1.
I appreciate any help you can offer.
Thanks,
Wing

Hi Brian,
Use of large pages does not impact other parameters within TimesTen; you don't need to change anything with regard to stuff like hash index pages etc. since these are TimesTen 'internal' pages not O/S memory pages. I also do not think use of large pages impacts other kernel parameters such as shmall (I don't recall ever havign to change those when using large pages).
In order for TimesTen to use large pages several things are required:
1. The kernel must be configured to enable a suitable number of large pages (vm/nr_hugepages). The way you are doing this is fine but obviously for 'production' use you would configure this in /etc/sysctl.conf (or equivalent)
2. The TT daemon must be told to use large pages via the -largePageALignment option (you are doing that too).
3. The number of large pages configured must be large enough to contain the entire TT datastroe segment (PermSize+TempSize+LogBuffSize+~20 Mb). You can see the exact size of the segment via 'ipcs -m'.
4. The kernel parameter vm/hugetlb_shm_group must be set to the O/S groupid which the user under which the TT main daemon is executing is a member of. For example, I havea group called timesten (gid = 1000) and the Tt instance administrator user is a member og that group. I have vm.hugetlb_shm_group = 1000.
With all this in place my datastores use large pages with no problem (as confirmed by cat /proc/meminfo after the datastore is loaded). This is all you need to do, nothing more.
Chris

Similar Messages

Large pages are not used when databases are started from srvctl on ibm aix

Hi,
RAC 11.2.0.3.2 on IBM AIX 6.1 TL07. Mixed databases 10.2.0.5.4 and 11.2.0.3.2
When started with SQLPLUS, the database instance use LARGE PAGES
When started with SRVCTL, the database instance doesn't use LARGE PAGES, even root has the right capabilities
lsuser -a capabilities root
root capabilities=CAP_NUMA_ATTACH,CAP_BYPASS_RAC_VMM,CAP_PROPAGATE
The same behaviour is observed for 10.2.0.5.4 and 11.2.0.3.2 databases.
ORACLE_SGA_PGSZ=16m is exported in /etc/profile.
I found that :
1) When the node is restarted (shutdown -r now), clusterware and all databases (database 10gr2, 11gr2 , asm, ...) start automaticaly WITHOUT using LARGE PAGES. After this, databases restarted with SQLPLUS are USING LARGE PAGES, and databases restarted with SRVCTL NEVER use LARGE PAGES.
2) When the clusterware is restarted manualy (crsctl stop|start crs) all databases (database 10gr2, 11gr2 , asm, ...) start automaticaly and all instances (10gr2 and 11gr2) are USING the LARGE PAGES. After this, database are ALWAYS using LARGE PAGES (started with SQLPLUS or SRVCTL)
So, this problem occurs only after a restart of the host. All is fine after a manual restart of the clusterware.
my references
SGA Not Pinned In The AIX Large Pages When Instance Is Started With Srvctl [ID T369424.1]
How to enable Large Page Feature on AIX-Based Systems [ID 372157.1]
Thank's for your help

The problem here is for IBM AIX (I dont find the equivalent for ulimit -l max locked memory, in ulimit for AIX)
Here a portion of the original /etc/ohasd script (ulimit -c and -n are already set for AIX)
start_stack()
# see init.ohasd.sbs for a full rationale
case $PLATFORM in
Linux)
# MEMLOCK limit is for Bug 9136459
ulimit -l unlimited
ulimit -c unlimited
ulimit -n 65536
ulimit -c unlimited
ulimit -n 65536
esac
So i put a trace
start_stack()
# see init.ohasd.sbs for a full rationale
case $PLATFORM in
Linux)
# MEMLOCK limit is for Bug 9136459
ulimit -l unlimited
ulimit -c unlimited
ulimit -n 65536
ulimit -c unlimited
ulimit -n 65536
echo "$(ulimit -a)" > /tmp/coh.log
echo "$(lsuser -a capabilities root)" >> /tmp/coh.log
esac
here is the result :
time(seconds) unlimited
file(blocks) unlimited
data(kbytes) unlimited
stack(kbytes) 4194304
memory(kbytes) unlimited
coredump(blocks) unlimited
nofiles(descriptors) 65536
threads(per process) unlimited
processes(per user) unlimited
root capabilities=CAP_NUMA_ATTACH,CAP_BYPASS_RAC_VMM,CAP_PROPAGATE
i continue investigating this way ...

Can large page improve timesten performance on aix??

hello, chris:
Can large page imporove timesten performance on aix? we havenot test it yet, I just want to know whether it is ok?? thank you.

Enabling large page support on AIX may help performance under some circumstances (typically with large datastores). TimesTen does support use of large pages on AIX and no special action is needed on the TimesTen side to utilise large pages. Here is some information on this which should eventually appear in the TimesTen documentation.
The TimesTen shared memory segment for AIX has been created with the flags
( SHM_PIN | SHM_LGPAGE) necessary for large page support for many releases.
It used to be the case that special kernel flags needed to be enabled so it
was never documented as being supported. Subsequent AIX releases have made
enabling large pages a matter of system administration.
1) Enable capabilities (chuser)
2) Configure page pool (vmo -r)
3) Enable memory pining (vmo -p)
4) [restart timesten daemons]
The documentation is quoted below.
AIX maintains separate 4 KB and 16 MB physical memory pools. You can
specify the amount of physical memory in the 16 MB memory pool using the vmo
command. Starting with AIX 5.3, the large page pool is dynamic, so the amount
of physical memory that you specify takes effect immediately and does not
require a system reboot. The remaining physical memory backs the 4 KB virtual
pages.
AIX treats large pages as pinned memory. AIX does not provide paging
support for large pages. The data of an application that is backed by large
pages remains in physical memory until the application completes. A security
access control mechanism prevents unauthorized applications from using large
pages or large page physical memory. The security access control mechanism
also prevents unauthorized users from using large pages for their
applications. For non-root user ids, you must enable the CAP_BYPASS_RAC_VMM
capability with the chuser command in order to use large pages. The following
example demonstrates how to grant the CAP_BYPASS_RAC_VMM capability as the
superuser:
# chuser capabilities=CAP_BYPASS_RAC_VMM,CAP_PROPAGATE <user id>
The system default is to not have any memory allocated to the large page
physical memory pool. You can use the vmo command to configure the size of
the large page physical memory pool. The following example allocates 4 GB to
the large page physical memory pool:
# vmo -r -o lgpg_regions=64 -o lgpg_size=16777216
To use large pages for shared memory, you must enable the SHM_PIN shmget()
system call with the following command, which persists across system reboots:
# vmo -p -o v_pinshm=1
To see how many large pages are in use on your system, use the vmstat -l
command as in the following example:
# vmstat -l
kthr memory page faults cpu large-page
r b avm fre re pi po fr sr cy in sy cs us sy id wa alp flp
2 1 52238 124523 0 0 0 0 0 0 142 41 73 0 3 97 0 16 16
From the above example, you can see that there are 16 active large pages, alp, and
16 free large pages, flp.
Documentation is at:
http://publib.boulder.ibm.com/infocenter/pseries/v5r3/index.jsp?topic=/com.ibmaix.prftungd/doc/prftungd/large_page_ovw.htm
Chris

Large pages for SHM

Hello,
can you help me with this: I want to create a SHM region that uses 4mb large pages. If possible, I want the OS to choose the virtual address to place the SHM segment. However, I've read that it has to be aligned on 4mb boundaries.
The code to create the SHM segment looks like this:
id = shmget(13235, 16*1024*1024, IPC_CREAT | 0666);
shm = shmat(id, (void *)0, 0);How would I advise the OS to use 4mb pages for this segment?
Thanks,
Nick.

Hi,
in the meantime I tried to code something. It turned out that in my little test program the address returned by shmat is aligned to 4mb boundaries by accident... Therefore I just tried to make the pages 4mb large, but it didn't work: memcntl returned with errno == EINVAL, and I don't know why.
This is my code:
#include <stdio.h>
#include <stdlib.h>
#include <errno.h>
#include <sys/types.h>
#include <sys/ipc.h>
#include <sys/shm.h>
#include <sys/mman.h>
#define MEGABYTE ((size_t)(1024 * 1024))
#define FOUR_MEGABYTE ((size_t)4 * MEGABYTE)
int main() {
int id;
char *shm;
char c;
int i;
struct memcntl_mha mha;
fprintf(stderr,"memcntl error codes\n");
fprintf(stderr,"EINVAL : %d\n",EINVAL);
mha.mha_cmd = MHA_MAPSIZE_VA;
mha.mha_flags = 0;
mha.mha_pagesize = FOUR_MEGABYTE;
if ((id = shmget(13235, 16*1024*1024, IPC_CREAT | 0666)) == -1) {
    fprintf(stderr, "shmget: shmget failed\n");
    return(1);
} else {
    fprintf(stderr, "shmget successful: shmget returned %d\n", id);
if((shm = shmat(id, (void *)0, 0)) == (char *)-1) {
    fprintf(stderr, "shmat: shmat failed\n");
    return(1);
} else {
    fprintf(stderr, "shmat successful: %u\n",shm);
if ((((uintptr_t)(shm)) & ((uintptr_t)(FOUR_MEGABYTE) - 1)) == 0) {
    fprintf(stderr, "address %u is aligned\n",shm);
} else {
    fprintf(stderr, "address %u is NOT aligned\n",shm);
if (memcntl(shm, 16*1024*1024, MC_HAT_ADVISE, (char *)&mha, 0, 0) < 0) {
    fprintf(stderr, "memcntl failed: %d\n",errno);
} else {
    fprintf(stderr, "memcntl succeeded\n");
for (i=0; i<16*1024; i++) shm[i*1024] = 'a';
printf("Hit a key.\n");
scanf("%c", &c);
if (shmdt(shm) == -1) {
    fprintf(stderr, "shmdt failed\n");
} else {
    fprintf(stderr, "shmdt successful\n");
if (shmctl(id, IPC_RMID, 0) < 0) {
    fprintf(stderr, "shmctl failed\n");
} else {
    fprintf(stderr, "shmctl successful\n");
return(0);
}This program produces the following output:
memcntl error codes
EINVAL : 22
shmget successful: shmget returned 2780004
shmat successful: 4261412864
address 4261412864 is aligned
memcntl failed: 22
Hit a key.
shmdt successful
shmctl successfulWith "pmap -sx <pid>" I see that the SHM segment is 16 mb large and consists only of 8kb pages.
Nick.

Using large pages on Solaris 10

Hello,
I�ve some problems to use large pages ( 16k, 512k, 4M ) on two Primepower650 systems. I�ve installed the most actual kernel 127111-05.
The pagesize -a command respond 4 page sizes ( 8k, 16k, 512k, 4M ). Even if I try the old manual method using LD_PRELOAD=mpss.so.1 and a mpss.conf file to force large pages the pmap -sx <pid> shows only 8k for stack,heap and anon. Only for shared memory 4M DISM segments are used. I didn�t receive any error message. Two other primepower systems with the same kernel release works as expected.
What can I do for further troubleshooting ? I�ve tried different kernel settings all without effect.
Best regards
JCJ

This problem is now ( paritially ) solved by the Fujitsu-Siemens edition of kernel patch 127111-08. The behaviour is now like Solaris 9 because large pages must be forced by LD_PRELOAD=mpss.so.1 and still didn�t work out of the box for this kind of cpu ( Sparc GP64 V only ). All available page sizes ( 8k, 64k, 512k and 4M ) can now be used by configuring the /etc/mpss.conf. Unfortunally large pages out-of-the-box are not working on this kind of cpu and the actual kernel patch. This is not so nice because on large systems with a lot of memory and a lot of large processes there may be still a lot of TLB misses. So I still wait and test further as soon as new kernel patches are available.
JCJ

How to use large pages in AIX with oracle

Hi,
i'm trying to convince oracle to use large pages on AIX 5.3 but haven't
suceeded so far.
i set v_pinshm=1, maxpin%=80, lgpg_regions=448 and lgpg_size=16777216
using 'vmo' and 'LOCK_SGA=true' in spfile. after rebooting and starting
the instance 'svmon' shows no no large pages in use:
# svmon
size inuse free pin virtual
memory 4046848 3711708 335140 2911845 1503108
pg space 524288 5551
work pers clnt lpage
pin 1076604 0 233 1835008
in use 1503010 0 373690 0
pgsize size free
lpage pool 16 MB 448 448
SGA size is 3G. why doesn't oracle use large pages? i already have
created a TAR but maybe an oracle-on-AIX expert can help me faster than
oracle support :)
regards,
-ap

Nice day Andreas,
please do you have some solution for your issue, because I think I have similar problem,
I set on AIX
vmo -r -o lgpg_regions=192 -o lgpg_size=16777216
vmo -o v_pinshm=1
I see in svmon -G this output
PageSize PoolSize inuse pgsp pin virtual
s 4 KB - 1104431 2456 685141 874874
L 16 MB 192 0 0 192 0
these (16MB large pages) are free but when I want run BEA WebLogic server run with parametr -Xlp the application is run with standard 4K memory pages,
thank you very much for any other hint,

Error: Java HotSpot(TM) 64-Bit Server VM warning: JVM cannot use large page

Hi,
i recently came across Error Message (coming up in webadmin Log view):
ProcessMonitor: Java HotSpot(TM) 64-Bit Server VM warning: JVM cannot use large page memory because it does not have enough privilege to lock pages in memory
when running Oracle NoSQL on Windows 7 64bit Home Premium system, having 8GB of physical RAM.
I created the store configuration without explicitly passing a value for parameter memory_mb (was set to -memory_mb 0), so that replication group would take as much
memory as possible, which found it's reflection in following line from store log:
Creating rg1-rn1 on sn1 haPort=tangel-lapp:5.011 helpers=tangel-lapp:5011 mountpoint=null heapMB=7.007 cacheSize=5.143.454.023 -XX:ParallelGCThreads=4
I was a bit surprised because of the fact that i definetly succeeded in running kvstore in this configuration, leading to store using 7007MB of memory.
It was only possible to run kvstore when creating store configuration with memory configured to be less than 2GB.
After searching google with error message mentioned above i came across some hints regarding activation of Huge Pages on Windows 7, which mentioned that it could be
done on systems having at least Windows 7 Professional Edition.
But finally i found a more helpful hint, referring to size of windows pagefile. As my machine uses an SSD as system disk and there some notes on deactivating pagefile when
using an SSD, i did so some time ago.
So i activated the pagefile on windows again and after doing so, the store came up without any problems.
Maybe it's nothing new to some of you guys, but as there was nothing to be read about this fact in neither admin nor getting started guide, i just wanted to share this
piece of information with you.
Regards
Thomas

Charles,
thanks for clarification, obviously i've overseen that in chapter "Installation prerequisites" of
Admin Guide.
By the way, are there any specific OS related settings, let's say "best practice" similar as it is
referred to in documentation of "classic" Oracle Databases?
Regards
Thomas

Total Shared Global Region in Large Pages = 0 KB (0%)

Hi ,
Am working on Oracle Database 11.2.0.3 ,
Application 12.1.3.
i see this message in the alert log file :
****************** Large Pages Information *****************
Total Shared Global Region in Large Pages = 0 KB (0%)
Large Pages used by this instance: 0 (0 KB)
Large Pages unused system wide = 0 (0 KB) (alloc incr 32 MB)
Large Pages configured system wide = 0 (0 KB)
Large Page size = 2048 KB
RECOMMENDATION:
Total Shared Global Region size is 12 GB. For optimal performance,
prior to the next instance restart increase the number
of unused Large Pages by atleast 6145 2048 KB Large Pages (12 GB)
system wide to get 100% of the Shared
Global Region allocated with Large pages
What should i do ?
Thanks

You definitely are not using hugepagesd. That's what the message you mentioned above is telling you:
Total Shared Global Region in Large Pages = 0 KB (0%)It very clearly tells you that you have 0KB or 0% is in large pages.
Note that the terms "large pages" and "hugepages" are synonymous. In Linux, they're called hugepages.
Also, at the O/S level, you can do:
cat /proc/meminfoTo see how many hugepages are allocated/free/reserved.
Hope that helps,
-Mark

Maximum Large Pages

Hi
I have RHEL 6.4 with 128GB RAM
I have big database
The database is the only service on this box.
what is the optimal number of large pages I can have in the box ?
(to not disturb the OS )
Tanks for your help

> I have RHEL 6.4 with 128GB RAM
> I have big database
> The database is the only service on this box.
> what is the optimal number of large pages I can have in the box ?
Depends what you want.
Based on the information you have supplied, I would recommend a HugePages value between 0 GB and 127 GB.
How large is your application?
What kind of application is it?
What is the locality in its data access? Sequential? Random?
How long should any cached data be kept in memory just in case it is needed again?
How much data does the application need to read and write?
The DB install guide has some recommendations on calculating the size of the shared global area (SGA); use them.
Do not enable Automatic Memory Management (AMM) because AMM is just a poor-man's HugePages.
Does your DB use many table joins? Few joins but lots and lots of data rows?
Remember your SGA must fit entirely within the HugePages area else you will get massively-degraded performance.
I have RHEL 6.4 with 128GB RAM
I have big database
The database is the only service on this box.
what is the optimal number of large pages I can have in the box ?

Large Pages setting

Hello all,
We recently created a new 11.2.0.3 database on Red Hat Linux 5.7. It's running in ASMM
Database settings
sga_target set to 10G
sga_max=12G
memory_target=0.
memory_max=0
pga_aggregate_target =12G.
Host Specs
Total RAM = 128GB
Total CPUs = 4 @ 2.27GHz
Cores/CPU = 8
During instance startup, we get the following message.
****************** Large Pages Information *****************
Total Shared Global Region in Large Pages = 0 KB (0%)
Large Pages used by this instance: 0 (0 KB)
Large Pages unused system wide = 0 (0 KB) (alloc incr 32 MB)
Large Pages configured system wide = 0 (0 KB)
Large Page size = 2048 KB
RECOMMENDATION:
Total Shared Global Region size is 12 GB. For optimal performance,
prior to the next instance restart increase the number
of unused Large Pages by atleast 6145 2048 KB Large Pages (12 GB)
system wide to get 100% of the Shared
Global Region allocated with Large pages
Has anyone seen this recommendation message during startup and acted upon it? if yes, what kind of modification was performed.
Thanks for your time.

From 11.2.0.2 new parameter was added i.e use_large_pages, now whenever the database instance is started it will check for huge pages configuration and there for produce the warning if Oracle will allocate part of the SGA with hugepages and the resting part with normal 4k pages.
USE_LARGE_PAGES parameter has three possible values "true" (default), "only", and "false".
The default value of "true" preserves the current behavior of trying to use hugepages if they are available on the OS. If there are not enough hugepages, small pages will be used for SGA memory.
This may lead to ORA-4031 errors due to the remaining hugepages going unused and more memory being used by the kernel for page tables.
Setting it to "false" means do not use hugepages
A setting of "only" means do not start up the instance if hugepages cannot be used for the whole memory (to avoid an out-of-memory situation).
There is not much written about this yet, but i'm able to find some docs in metalink and from blogs. Hope this help.
Large Pages Information in the Alert Log [ID 1392543.1]
USE_LARGE_PAGES To Enable HugePages In 11.2 [ID 1392497.1]
NOTE:361323.1 - HugePages on Linux: What It Is... and What It Is Not...
Bug 9195408 - DB STARTUP DOES NOT CHECK WHETHER HUGEPAGES ARE ALLOCATED- PROVIDE USE_HUGEPAGES
http://agorbyk.wordpress.com/2012/02/19/oracle-11-2-0-3-and-hugepages-allocation/
http://kevinclosson.wordpress.com/category/use_large_pages/
http://kevinclosson.wordpress.com/category/oracle-automatic-memory-management/

Large page sizes on Solaris 9

I am trying (and failing) to utilize large page sizes on a Solaris 9 machine.
# uname -a
SunOS machinename.lucent.com 5.9 Generic_112233-11 sun4u sparc SUNW,Sun-Blade-1000
I am using as my reference "Supporting Multiple Page Sizes in the Solaris� Operating System" http://www.sun.com/blueprints/0304/817-6242.pdf
and
"Taming Your Emu to Improve Application Performance (February 2004)"
http://www.sun.com/blueprints/0204/817-5489.pdf
The machine claims it supports 4M page sizes:
# pagesize -a
8192
65536
524288
4194304
I've written a very simple program:
main()
int sz = 10*1024*1024;
int x = (int)malloc(sz);
print_info((void**)&x, 1);
while (1) {
int i = 0;
while (i < (sz/sizeof(int))) {
x[i++]++;
I run it specifying a 4M heap size:
# ppgsz -o heap=4M ./malloc_and_sleep
address 0x21260 is backed by physical page 0x300f5260 of size 8192
pmap also shows it has an 8K page:
pmap -sx `pgrep malloc` | more
10394: ./malloc_and_sleep
Address Kbytes RSS Anon Locked Pgsz Mode Mapped File
00010000 8 8 - - 8K r-x-- malloc_and_sleep
00020000 8 8 8 - 8K rwx-- malloc_and_sleep
00022000 3960 3960 3960 - 8K rwx-- [ heap ]
00400000 6288 6288 6288 - 8K rwx-- [ heap ]
(The last 2 lines above show about 10M of heap, with a pgsz of 8K.)
I'm running this as root.
In addition to the ppgsz approach, I have also tried using memcntl and mmap'ing ANON memory (and others). Memcntl gives an error for 2MB page sizes, but reports success with a 4MB page size - but still, pmap reports the memcntl'd memory as using an 8K page size.
Here's the output from sysinfo:
General Information
Host Name is machinename.lucent.com
Host Aliases is loghost
Host Address(es) is xxxxxxxx
Host ID is xxxxxxxxx
/opt/default/bin/sysinfo: /dev/ksyms is not a 32-bit kernel namelist
Manufacturer is Sun (Sun Microsystems)
/opt/default/bin/sysinfo: /dev/ksyms is not a 32-bit kernel namelist
/opt/default/bin/sysinfo: /dev/ksyms is not a 32-bit kernel namelist
System Model is Blade 1000
/opt/default/bin/sysinfo: /dev/ksyms is not a 32-bit kernel namelist
ROM Version is OBP 4.10.11 2003/09/25 11:53
Number of CPUs is 2
CPU Type is sparc
App Architecture is sparc
Kernel Architecture is sun4u
OS Name is SunOS
OS Version is 5.9
Kernel Version is SunOS Release 5.9 Version Generic_112233-11 [UNIX(R) System V Release 4.0]
/opt/default/bin/sysinfo: /dev/ksyms is not a 32-bit kernel namelist
Kernel Information
/opt/default/bin/sysinfo: /dev/ksyms is not a 32-bit kernel namelist
SysConf Information
Max combined size of argv[] and envp[] is 1048320
Max processes allowed to any UID is 29995
Clock ticks per second is 100
Max simultaneous groups per user is 16
Max open files per process is 256
System memory page size is 8192
Job control supported is TRUE
Savid ids (seteuid()) supported is TRUE
Version of POSIX.1 standard supported is 199506
Version of the X/Open standard supported is 3
Max log name is 8
Max password length is 8
Number of processors (CPUs) configured is 2
Number of processors (CPUs) online is 2
Total number of pages of physical memory is 262144
Number of pages of physical memory not currently in use is 4368
Max number of I/O operations in single list I/O call is 4096
Max amount a process can decrease its async I/O priority level is 0
Max number of timer expiration overruns is 2147483647
Max number of open message queue descriptors per process is 32
Max number of message priorities supported is 32
Max number of realtime signals is 8
Max number of semaphores per process is 2147483647
Max value a semaphore may have is 2147483647
Max number of queued signals per process is 32
Max number of timers per process is 32
Supports asyncronous I/O is TRUE
Supports File Synchronization is TRUE
Supports memory mapped files is TRUE
Supports process memory locking is TRUE
Supports range memory locking is TRUE
Supports memory protection is TRUE
Supports message passing is TRUE
Supports process scheduling is TRUE
Supports realtime signals is TRUE
Supports semaphores is TRUE
Supports shared memory objects is TRUE
Supports syncronized I/O is TRUE
Supports timers is TRUE
/opt/default/bin/sysinfo: /dev/ksyms is not a 32-bit kernel namelist
Device Information
SUNW,Sun-Blade-1000
cpu0 is a "900 MHz SUNW,UltraSPARC-III+" CPU
cpu1 is a "900 MHz SUNW,UltraSPARC-III+" CPU
Does anyone have any idea as to what the problem might be?
Thanks in advance.
Mike

I ran your program on Solaris 10 (yet to be released) and it works.
Address Kbytes RSS Anon Locked Pgsz Mode Mapped File
00010000 8 8 - - 8K r-x-- mm
00020000 8 8 8 - 8K rwx-- mm
00022000 3960 3960 3960 - 8K rwx-- [ heap ]
00400000 8192 8192 8192 - 4M rwx-- [ heap ]
I think you don't this patch for Solaris 9
i386 114433-03
sparc 113471-04
Let me know if you encounter problem even after installing this patch.
Saurabh Mishra

Large page format PDF Cropping

Hi I have recently upgraded to CS5. I am using a Mac Quad Core Intel Xeon with Snow lepoard OS.
My problem is that im trying to PDF a large page size from Indesign, i go through the usual chanel of print setup, i click on Manage Custom Sizes
Enter the new size, return to the setup window ensure every thing is to 100 % scale crop mark etc and save as post script. i then take the document into distiller. The output is an A3 cropped version of the bottom left corner.
I have read Snow lepoard is not dependant on the PDF Wrtiter print drive any more? so should i use my Laser printer driver with the bespoke page size? there seems to be little or contradictory information on this subject.
If any one could offer some insight i would be most grateful. Thanks

This is really an InDesign issue and not PDF, but I'll answer.
Use File->Export to create the PDF.
Creation of PDF from Creative Suite applications should ALWAYS be done using Export/Save As and NEVER using printing.

Windows 7 - Large Pages

While I was performing some benchmarks on my W520, I became aware that there is a function in Windows 7 called Large Pages. Essentially setting this policy for either a single user or a group greatly reduces the TLB overhead when translating memory addresses for applications in storage. The normal page size is 4KB. Large Pages sets the page size to be 2MB. The smaller number was useful when there was only a relatively small physical memory space available in the system (Windows 95, etc). However, as the addressable physical page space becomes larger, the overhead for translating addresses across page boundaries starts to be significant. Linux has an equivalent function.
Here's a screenshot of where the setting (Lock pages in memory) is located:
<----------------
The memory bandwidth benchmark using SiSoftware Sandra 2012 showed a performance increase of 2.04% for normal operations and a 2.9% increase for floating point operations. This was with only one user enabled. Enabling all users in the system brought an additional .5% performance increase. PCMARK7 also showed a corresponding increase in benchmark performance numbers.
Thanks to Huberth for pointing me into the SiSoftware Sandra 2012 benchmarking software and the memory bandwidth warning.
This is an extract from a memory bandwidth benchmark run:
Integer Memory Bandwidth
Assignment : 16.91GB/s
Scaling : 17GB/s
Addition : 16.75GB/s
Triad : 16.72GB/s
Data Item Size : 16bytes
Buffering Used : Yes
Offset Displacement : Yes
Bandwidth Efficiency : 80.36%
Float Memory Bandwidth
Assignment : 16.91GB/s
Scaling : 17GB/s
Addition : 16.73GB/s
Triad : 16.74GB/s
Data Item Size : 16bytes
Buffering Used : Yes
Offset Displacement : Yes
Bandwidth Efficiency : 80.34%
Benchmark Status
Result ID : Intel Core (Sandy Bridge) Mobile DRAM Controller (Integrated Graphics); 2x 16GB Crucial CT102464BF1339M16 DDR3 SO-DIMM (1.33GHz 128-bit) PC3-10700 (9-9-9-24 4-33-10-5)
Computer : Lenovo 4270CTO ThinkPad W520
Platform Compliance : x64
Total Memory : 31.89GB
Memory Used by Test : 16GB
No. Threads : 4
Processor Affinity : U0-C0T0 U2-C1T0 U4-C2T0 U6-C3T0
System Timer : 2.24MHz
Page Size : 2MB
W520, i7-2820QM, BIOS 1.42, 1920x1080 FHD, 32 GB RAM, 2000M NVIDIA GPU, Samsung 850 Pro 1TB SSD, Crucial M550 mSata 512GB, WD 2TB USB 3.0, eSata Plextor PX-LB950UE BluRay
W520, i7-2760QM, BIOS 1.42 1920x1080 FHD, 32 GB RAM, 1000M NVIDIA GPU, Crucial M500 480GB mSata SSD, Hitachi 500GB HDD, WD 2TB USB 3.0

What kind of software do you use for the conversion to pdf? Adobe Reader can't create pdf files.

RAC windows 2003 64bit xeon - Large Pages

Hi all
i have 2 node (windows 2003 64bit dual core xeon, 8GB RAM)
oracle recommendet use large pages on 64bit insted LOCK_SGA, but when i use large pages and i set my sga_target=5GB after few minute in EM i see alert (stronicowanie virtual memory) i dont knew how i can write this, mayby swapping.
how can avoid this?
how i can check that oracle use large pages?
meyby some intresting links?
thanks to advice

You don't run a scalability option on a basically unscabable O/S like Winblows, do you?
Sybrand Bakker
Senior Oracle DBA

How to manage large pages

Just wondering... What is a good way to manage large pages?
Let's say a page with a pannelTabbed with 7 or 8 tabs. Each tab shows a table that is bound to a different VO. Most of the tabs also have a add,delete,edit button and i'm using popups for that.
So as you can see, their will be lots of bindings and lots of components on such a page.
If i create all this on a single page i think it will be a few thousands of lines which is not realy nice...
Should i create page fragments or create taskflows per tab or something like that?
Currently i have created the page with just the panelTabbed and then for each tab i created a taskflow and dropped that inside the showDetailItem. For each popup, i also created a taskflow so i could reuse it later when i need the same popup in other pages.
I'm wondering... what is a correct approach for such large pages. Are their any guidlines for this?

Hi,
we decided to use dynamic regions (11g) for our application.
This means we only have 1 jspx for the whole application and exchange the content at runtime.
For each "block" (e.g. a table, a tab or a popup) we have a single page fragment and task flow.
One page fragment consists normaly only of one view object.
With this concept we can reuse e.g. the same (similar) table on different pages too.
Hope this helps.
regards
Peter

Using hugepages (Large Pages)

Similar Messages

Maybe you are looking for