SPM-PPI中文说明

网络广告术语中英对照表及解释网络广告术语中英对照表及解释：1. CPM (Cost Per Mille) - 千次展示成本The cost an advertiser pays for one thousand ad impressions.2. CPC (Cost Per Click) - 每次点击成本The cost charged to an advertiser for each click on their ad.3. CPA (Cost Per Action) - 行动成本The cost an advertiser pays for each desired action taken as a result of their ad, such as a purchase or sign-up.4. CTR (Click-Through Rate) - 点击率The ratio of users who click on an ad compared to the total number of users who view the ad.5. ROI (Return on Investment) - 投资回报率The profitability of an advertising campaign or investment, calculated as a percentage of the return compared to the cost.6. Impressions - 展示量The number of times an ad is displayed to users.7. Reach - 达到人数The total number of unique users or audience members who have been exposed to an ad.8. Conversion - 转化The act of a user completing a desired action as a result of an ad, such as making a purchase or filling out a form.9. Banner Ad - 横幅广告A graphic ad that typically appears across the top, bottom, or side of a web page.10. Native Ad - 原生广告An ad that matches the form and function of the platform it appears on, providing a seamless user experience.11. Retargeting - 重新定位A strategy that displays ads to users who have previously visiteda website, in order to keep the brand or product top of mind.12. A/B Testing - A/B 测试A method of testing two versions of an ad or webpage to determine which one performs better.13. Click Fraud - 点击欺诈Illegitimate clicks on ads generated by manual or automated means, often in order to inflate click numbers or exhaust an ad budget.14. CTA (Call-to-Action) - 行动号召A statement or instruction that encourages users to take a specific action, typically included in an ad or landing page.15. Ad Blocker - 广告拦截器Software or browser extensions that prevent ads from being displayed to users.16. Landing Page - 落地页The specific webpage that a user is directed to after clicking onan ad or call-to-action.17. Organic Traffic - 自然流量The visitors to a website that come from unpaid, non-advertising sources, such as search engine results or direct visits.18. Keyword - 关键词A word or phrase that users search for, and that advertisers can bid on to have their ads shown when those keywords are used.19. Sponsored Content - 赞助内容Content that is created or promoted by an advertiser in collaboration with a publisher, with the goal of reaching a specific audience.20. Programmatic Advertising - 程序化广告Automated buying and selling of online ad impressions,typically using real-time bidding algorithms.请注意：术语中文解释为了简洁明了可能不是完全准确的，请根据具体上下文和需求，参考上述解释的基本意义。

优化操作数选解释一基本光学特性EFFL--有效焦距，以镜头长度单位表示。

它是针对近轴系统的，对于非近轴系统可能会不准确.PIMH--在指定波长的近轴像面上的像高PMAG--近轴放大率AMAG--角放大率。

这是像空间和物空间之间的近轴主光线角度的比值。

对于非近轴系统无效.ENPP--相对于第一个面的入瞳位置，以镜头长度单位表示。

这是近轴光瞳位置，仅对中心系统有效.EXPP--相对于第一个面的出瞳位置，以镜头长度单位表示。

这是近轴光瞳位置，仅对中心系统有效.LINV--系统的Lagrange 不变量，WFNO--工作F/#POWR--指定编号的表面的权重EPDI--入瞳口径，以镜头长度单位表示ISFN---像空间F/#EFLX--在现定X 平面上的，指定范围内的表面的主波长的有效焦距，以镜头长度单位表示.EFLY--在现定Y 平面上的，指定范围内的表面的主波长的有效焦距，以镜头长度单位表示.SFNO--在任意定义视场和波长时计算的弧矢工作F/#TFNO--在任意定义视场和波长时计算的弧矢工作F/#二像差SPHA --指定表面产生的球差贡献值COMA--指定表面产生的彗差贡献值，以波长表示。

如果表面编号值为0，则是针对整个系统。

这是由塞得和数计算得到的第三级彗差，对非近轴系统无效ASTI--指定表面产生的像散贡献值，以波长表示。

如果表面编号值为0，则是针对整个系统。

这是由塞得和数计算得到的第三级色散，对非近轴系统无效FCUR ---指定表面产生的场曲贡献值DIST--指定表面产生的畸变贡献值，以波长表示。

如果表面编号值为0，则使用整个系统。

同样，如果表面编号值为0，则畸变以百分数形式给出。

这是由塞得系数计算出的第三级畸变，对与非近轴系统无效DIMX--最大畸变值。

它与DIST 相似，只不过它仅规定了畸变的绝对值的上限。

视场的整数编号可以是0，这说明使用最大的视场坐标，也可以是任何有效的视场编号。

注意，最大的畸变不一定总是在最大视场处产生。

SPC、Cpk、Ppk的简介1. 什么是SPC？SPC，即统计过程控制（Statistical Process Control），是一种通过统计方法来分析和控制过程的方法。

它的目标是通过监控和控制过程中的变异性，确保产品和过程能够始终处于可控状态，并且能够满足规定的质量要求。

SPC通过收集数据、绘制控制图和运用统计方法来监控过程变异性，识别特殊因素对过程的影响，并采取相应的纠正措施。

SPC可以帮助组织实现质量管理的目标，提高产品质量、降低成本以及提高客户满意度。

2. 什么是Cpk？Cpk是一种衡量过程能力的指标，它用来评估一个过程是否具备满足特定要求的能力。

Cpk是一个包含了过程平均值与规格限之间差距和过程变异性的综合指标，它可以帮助我们了解一个过程的稳定性和能力。

Cpk的计算公式为：Cpk = Min((USL - μ) / (3σ), (μ - LSL) / (3σ))其中，USL是上规格限，LSL是下规格限，μ是过程平均值，σ是过程稳定性的标准差。

Cpk的值越大，说明过程的能力越高，即越有能力生产出符合规格要求的产品。

3. 什么是Ppk？Ppk也是一种衡量过程能力的指标，它和Cpk类似，但是Ppk考虑了过程能力的上下限是否对称的因素。

当一个过程的规格限对称时，Cpk和Ppk的值是相等的；当规格限不对称时，Ppk会比Cpk更能反映出过程的实际能力。

Ppk的计算公式为：Ppk = Min((USL - x̄) / (3δ), (x̄ - LSL) / (3δ))其中，USL是上规格限，LSL是下规格限，x̄是过程的平均值，δ是过程的标准差。

和Cpk类似，Ppk的值越大，说明过程的能力越高，即越有能力生产出符合规格要求的产品。

4. SPC、Cpk和Ppk的关系SPC是一种方法论，用于监控和控制过程的变异性；而Cpk和Ppk则是通过统计分析来评估一个过程的能力。

它们之间存在着紧密的关系。

SPC可以帮助我们收集数据，绘制控制图，并运用统计方法来监控过程变异性。

轻敲模式TAFM专业词汇：1.多模式：MultiMode2.轻敲扫描力显微镜：dynamic force AFM3.INO零点：Reset IN04.A/D通道调零：Reset A/D5.光斑检测：PSD(Position sensitive Detector) Alignment6.起伏信号：Vertical signal7.扭曲信号：lateral signal8.激光能量: Laser energy9.扫描控制面板：Scan Controls panel10.扫描范围：Scan size11.XY比率：XY ratio12.X偏移：X offset13.扫描角度: Scan direction14.扫描速率: Scan rate15.慢扫描使能：Slow scan axis enabled16.反馈控制面板：Feedback Controls panel17.比例增益：P. Gain18.积分增益：I.Gain19.设置点：Setpoint20.振源频率：Osc frequency21.振源幅度：Osc amplitude22.输入增益：Intput Gain23.反馈环路：Feedback loop24.开环：Feedback off25.闭环：Feedback on26.f-RMS曲线：Frequency-RMS Amplitude Curve27.f-RMS曲线控制面板：Frequency-RMS Amplitude Curve control panel28.频率扫描：Frequency sweep29.频率起点：Start frequency30.扫描范围：Sweep range31.工作频率：Driving frequency32.RMS 设置点：setpoint33.显示范围：display size34.自动搜索共振峰：Auto tune35.初始频率：start frequency36.结束频率：End frequency37.峰值要求：Peak amplitude38.反馈开环中，系统安全：Feedback off , system safe.39.马达自动控制：Auto Motor40.针尖-样品距离：Tip-Sample distance41.步数：count42.清零：Reset43.自动趋近：Approach44.自动退出：Withdraw45.单步进：Single step in46.单步退：Single step out47.样品移动: Sample diplacement48.步距：step size49.自动驱进停止在：stop at50.设置点自动调整阈值：Setpoint Threshold51.自动退出起始值：start to withdraw52.设置反馈：set feedback53.RMS-Z曲线: RMS-Z curve54.RMS-Z曲线控制面板：RMS-Z curve panel55.采样周期：sampling period56.扫描起点：Z scan start57.扫描范围：Z scan range58.显示范围：Data scale59.高度图像控制：Topography Image Control60.数据类型：Data mode61.显示模式：Display mode62.图像：image63.图像+剖面线：image + section64.实时校正模式:Realtime planefit65.线平均校正：Line66.偏置校正：Offset67.无校正：None68.显示范围：display size69.显示中心点：diplay center70.RMS信号:RMS signal71.起伏信号：vertical signal72.抬高模式：lift mode73.回扫高度：lift height74.磁力或静电力：magnetic force or electric force75.弹性常数：Spring constant76.扫描起点对Z标尺增量：scan start Z offset77.TAFM 探头：TAFM head。

photoshop分辨率的意思，分辨率是什么，颜⾊模式
photoshop分辨率是什么？
在PS中，分辨率是指决定图像精细程度的量级单位，即分辨率越⾼，图像就越精细，⼀般来说，分辨率表⽰单位长度内像素点的数量。

通常，分辨率的单位为PPI（像素/英⼨）。

分辨率的设置
通常，我们的图像是在显⽰器或者其他多媒体设备上显⽰时，分辨率设置为：72PPI （重点，标为重点的⼀定要记住）
当我们的图像是需要印刷时，则使⽤国际通⽤分辨率：300PPI （重点，标为重点的⼀定要记住）
海报⾼清写真 96~200 PPI
⼤型喷绘 25-50 PPI
photoshop颜⾊模式：
常⽤的颜⾊模式是：RGB、CMYK这两种（重点，标为重点的⼀定要记住）
RGB⾊彩模式是⼯业界的⼀种颜⾊标准，是通过对红（R）绿（G）蓝（B）三个颜⾊通道的变化以及它们相互之间的叠加来得到各式各样的颜⾊。

CMYK是另⼀个专门针对印刷业设定的颜⾊标准，是通过对青（C）、洋红（M）、黄（Y）、⿊（K）四种颜⾊变化以及它们相互之间的叠加来得到各种颜⾊的；
CMYK代表青、洋红、黄、⿊四种印刷专业的油墨颜⾊；在CMYK模式下PHOTSHOP通道中即为这四种颜⾊。

PPI（Pixel Per Inch）是图像分辨率所使用的单位，意思是：在图像中每英寸所表达的像素数目。

从输出设备（如打印机）的角度来说，图像的分辨率越高，所打印出来的图像也就越细致与精密。

DPI（Dot Per Inch）是打印分辨率使用的单位，意思是：每英寸所表达的打印点数。

DPI表示分辨率,指每英寸长度上的点数.DPI又可细分为水平分辨率和垂直分辨率,例如一张1英寸*1英寸的图片,如果它的水平分辨率是100 dpi,垂直分辨率是50 dpi,那么就是说,它水平每英寸分成100小段,垂直每英寸分成50小段,就像米尺上的一格格那样.这张图总共有100*50=5000个格子,这张图片共有5000像素.由于它的水平分辨率和垂直分辨率不相等,所以每个像素是一个微小的长方形.==============================所以像素实际上是一个面积的概念,而因为一般电脑/数码相机等生产出来的图片都是水平分辨率和垂直分辨率相等,每个像素是个微小的正方形,所以就讲成"DPI表示每英寸长度上的像数数目",其实就是"每英寸长度上的点数"了.每个像素的面积大小由生产工艺决定,工艺越高,每个像素面积越小,每平方英寸屏幕上就能容纳更多的像素,dpi值就越高,图像就越精细,像素小到人眼分辨不出的地步了,图像看起来就跟实际的没有分别了.数码相机的"多少多少万像素"的概念就是这样来的,比如说,一个相机最大可以拍出1600像素*1200像素的相片,它的像素值就是1600*1200=192万,约等于200万,这就是一台200万像素的数码相机了.于是问题中所讲的300 dpi就表示屏幕上水平和垂直的方向上每英寸的长度上都有300个点.这台机屏幕的实际高度要用像素数目和dpi结合起来算才能得出.对于这台机子,400像素就是400/300=1.33英寸,533像素就是533/300=1.78英寸.对于一张电脑照片，你可以在photoshop的“图像”--“图像大小”菜单那里改它的分辨率，默认是72，改小了就是缩小图片，改大了就是放大图片（图像质量有损失），其实就是放大缩小的效果而已，要说真正的影响，就是对一些要求分辨率高的图像打印输出场合的影响。

ppm广告之PPM介绍PPM（pre-productionmeeting，摄制前会议），是以合理的预算和有效的方法制作高质量的影视广告为会议主题，从1990年开始在全世界广告界启用的制度。

它可以统一广告主、广告公司和制作公司三方在影片风格、摄制方案和布景、演员等方面的意见，消除相互之间对一些拍摄细节的分歧，达成一种三方确认，形成共同的意愿和目的，减少制作过程中不必要的预算、时间和人力的浪费。

下面上海梧桐树影视公司为大家简答阐述一下PPM包含的内容。

PPM一般由广告公司的客户代表主持，他要对拍片事宜和三方主要人员都比较熟悉，并能把握会议的程序和节奏，以保证所有的议题都会被讨论到，提高会议的效率。

会议的内容就是对上面PPM报告中的事项逐一进行讨论。

1.创意还需不需要做一些小的修改？为什么？怎样修改？这些修改对制作费有没有影响？2.摄制分工是否合理，如不合理应如何重新分配？3.摄制日程中的进度是否需要调整？为什么？制作公司能否如期完成影片的摄制工作？4.对已挑选的演员是否满意？如不满意，应挑选什么样的演员（包括身高、脸型、身材和气质等）？5.对广告音乐要什么意见和要求？6.布景设计还需不需要修改？是需要局部修改，还是推倒重来？7.道具是否合适？各种道具具体的数量是多少？8.发饰、化妆和时装是否合适？9.需要多少产品样本？产品怎样操作？产品何时运到拍摄现场，交给谁？10.外景地是否符合要求？如不符合需要重新挑选一个怎样的外景地？11.最核心的部分：导演关于广告拍摄的阐述和拍摄内容的具体说明，各方是否满意？如不满意，需要做怎样的修改和调整？总之，所有拍摄事项和细节都要在会上予以充分的讨论，并需要最终达成一致的意见，并保证各方清楚地知道拍摄时需要自己履行的职责和如何具体实施，以免拍摄时扯皮、推诿和误解，以至于影响正常的拍摄工作。

广告公司和影视制作公司要记录PPM上确认、决定的事项，会后制作成类似会议纪要或者备忘录的报告，分发给参加会议的主要人士。

版本时间说明修订者V0.22014-12-16起草目录王成波快速使用指南零部件1附带SD卡的Pixhawk7电源模块2蜂鸣器8I²C分配器模块4SD卡USB适配器9四接口I²C分配器连接线5USB连接线10三线制伺服连接线6六线制连接线x211泡沫双面黏胶准备开始在APM固件的帮助下，Pixhawk能将任1安装何遥控飞机、直升机或者车辆变成多功能2连接私人飞机。

只要你有组装好的完整框架，3下载固件就可以遵照下面的指南安装Pixhawk。

4校正安装使用提供的泡沫双面胶将Pixhawk安装在飞机重心位置上。

注意确保Pixhawk上的箭头指向飞机前方。

将方形泡沫双面胶黏贴在飞控板的四个角上飞机正面购买在购买3DR整机框架和电子套件连接（要求）连接蜂鸣器和安全开关（可选项）使用3DR数传套件（要求）连接3DR GPS和罗盘，以提供飞机的飞行定位数里的六线制连接线将3DR无线据。

使用套件里提供的六线制连接线将罗盘连接到GPS接接收器连接到Pixhawk上的TE-口上；用四线制连接线，将MAG连接到I²C接口上。

LEM接口。

实现数据接收并与飞机进行实时交流。

（要求）使用6线制连接线将3DR电源模块连接到POWER接口上，利用锂聚合物（LiPo）电池直接向飞行器供电。

（可选项）I²C分配器扩展了I²C接口，使PiXhawk能连接多达四种的外设。

使用四线制连接线将分配器连接到Pixhawk上，并把罗盘模块、外部LED、数字空速传感器和其它外设添加到你的机架上。

了解更多在/learn了解LiPo电池及其供电机制。

连接无线控制模块PPM RC接收器使用三线制伺服连接线，将RC接口的三个管脚分别连接到地（—）、电源（+）和信号（S）。

FUTABA S.BUS接收器使用三线制伺服连接线，将RC接口的三个管脚分别连接到地（—）、电源（+）和信号（S）。

SPECTRUM卫星接收器PWM接收器在购买PPM解码器模块，将PWM RC接收器连接到Pixhawk上。

HP PPM Center White Paper -Understanding and Tuning the CacheVersion: 1.0October 2014Applies to PPM 9.10 and later.ContentsIntroduction (2)PPM Cache Overview (2)Comparison between Legacy Cache and New Cache (2)Understanding the PPM Cache Statistics reports (3)Legacy Cache (3)New Cache (3)PPM Cache Tuning (3)Flushing the PPM cache with kRunCacheManager.sh and ksc_flush_cache (5)kRunCacheManager.sh (5)Syntax (5)Issues & Limitations (6)ksc_flush_cache (6)Syntax (6)Issues & Limitations (6)PPM Cache changes in PPM 9.31 (6)Conversion from legacy cache to new cache (7)Simplification of new cache configuration (7)Changes to CacheManager Statistics report (7)Changes to kRunCacheManager.sh (7)Changes to ksc_flush_cache (8)More questions? Need help? (8)IntroductionThis document describes the PPM Cache architecture up to PPM 9.30, as well as the changes introduced to the Cache in PPM 9.31. It should help PPM Administrators to correctly tune PPM Caches in order to achieve optimal system performance.PPM Cache OverviewThere are two caches in PPM that can be tuned by PPM Administrators:-Legacy cache (Table Components, Request Type Search Fields, List Validation Values, etc.).It is configured in <PPM_HOME>/conf/tune.conf. Setting the parameters in server.conf works too and some of the parameters can be edited from the admin console.You can view its cache statistics in the “Server Cache Status” report in Workbench’s AdminTools.-New cache (Requests, Request Types, Modules, Portlets, Workflows, etc.).It is configured in <PPM_HOME>/conf/cache.conf.You can view cache statistics in the “CacheManager Statistics” report in Workbench’s AdminTools.Comparison between Legacy Cache and New CacheThe new cache has the following advantages over the legacy cache:-All cache objects are stored using java SoftReference. As a result, if the JVM runs out of Heap Memory, objects in the cache will be automatically garbage collected to free up memory. Thismakes it possible to store large amounts of data in the cache without risking out-of-memoryissues under heavy system load.-There are more cache configuration parameters (at least until PPM 9.31, in which new cache configuration has been simplified).-It is possible to invalidate a single object in the new cache by using ksc_flush_cache special command (which only works with new cache), whereas only full cache flush is possible whenusing kRunCacheManager.sh (which works with both legacy and new cache).-The new cache provides configurable staleness checks, whereas such checks are hard coded in the legacy cache.-More statistics in the Cache report (number of staleness checks, average load time, number of flushes of the different type).Understanding the PPM Cache Statistics reportsThe following information is available in the cache server reports.Legacy CacheFollowing information is available for each legacy cache in the “Server Cache Status Report”:∙Maximum number of objects that can be cached (Cache size)∙Number of additional objects that can be cached (Free units)∙Number of hits, misses and swaps (swaps meaning replace an object by another one when max size is reached)∙Miss rate (the lower, the better)∙Estimation of the amount of memory taken up by the cacheNew CacheFollowing information is available for each new cache in the “CacheManager Statistics Report”:∙Hits, misses, and hit rate (the higher the hit rate, the better)∙Number of cache flushes (broken down by the categories "old", "idle", "soft reference reclaimed", and "max cache size reached")∙Average load time to load an object from database when it is not in the cache∙Number of staleness checks performed∙Max cacheable objects (Cache size), cached object count and maximum idle time∙Whether the cache is distributed or not (if it is, removing an object from the cache in any node of the PPM cluster will send a message to all other cluster nodes to remove that object fromtheir cache).PPM Cache TuningTuning PPM Cache performance should be done at the same time as tuning PPM JVM Heap size. This means finding the right balance between 2 things:-JVM Heap size: Before PPM 9.20, only 32bits JVM was supported, which limited the JVM Heap size to ~1.3GB. Since PPM 9.20 and the adoption of 64bits JVM, the size of the JVM Heapmemory is only limited by the installed physical memory. However, too large Heap size canresult in long full garbage collection times, during which the application is unresponsive. It iscommon to see PPM JVM heap sizes of up to 4 GB, and sometimes more on Service nodes.-Caches size: A larger cache size means more cacheable objects, a better hit rate, and fewer objects to reload from the database, which result in better application performance. However, if cached objects end up taking too much memory, this will impact the performance of theapplication and might even cause out-of-memory problems. Note that only legacy cache isprone to causing such memory problems, as the JVM will automatically discard objects from the new cache whenever the available free memory runs too low.To summarize:-If JVM Heap size is too large, full garbage collection periods will be too long and application might become unresponsive for seconds, degrading users experience-If Caches are too large and end up using up too much memory, the performance of the application will degrade and in the case of legacy cache it might even cause out-of-memoryissues.Tuning your PPM cache can be done by following these steps, which may end up conflicting with each other; if that happens, use your best judgment.-If you see a high number of swaps (legacy cache) or “max cache size reached” flushes (new cache), increase the cache size.-If you see some “soft reference reclaimed” flushes (new cache), increase the JVM Heap or reduce the cache size for cache using up large amounts of space.-If you see a high miss rate (above 20%, legacy cache) or a low hit rate (below 80%, new cache) even after prolonged PPM usage (at least one day of heavy usage), increase the cache size.-If you notice long full garbage collection times (many seconds) during which the system is unresponsive, reduce the Heap size or better tune the JVM Garbage collection. Note that youwill need to use a JVM monitoring tools in order to ensure that JVM pause times are caused by full garbage collection.There are some additional tips that might help you when tuning the PPM cache:1)There is no “standard” cache configuration. Measure, tune, rince & repeat until you reachsatisfactory numbers. All PPM usages are different, and as a result caches configurations should be tuned accordingly.2)When tuning the PPM cache, try to do so after capturing statistics during the highest peak loadtime (usually happening on Friday afternoon or Monday morning). Tuning your cache onlymakes sense if it is tuned to properly handle peak load usage.3)Try not to flush the caches (using kRunCacheManager or ksc_flush_cache) in an automated wayunless you really have to. If using kRunCacheManager, NEVER use the “A” option to flush allcaches in an automated script; you should not flush more caches than necessary.4)If memory limit doesn’t allow you to set the proper max cache size for all the entities, you canrank the cache t o optimize first by the value “Average Load time” x “Misses”, and first increase the cache size of the cache(s) with the highest value. They are the most likely to have ameasurable performance impact.5)You might want to tune differently the PPM nodes in your cluster depending on whether theyare Service nodes or Web User only nodes. The entities loaded (and thus the optimal cachesettings) are different. For example, a pure Service node will never load portlets or menus, but might need a larger cache size for fiscal periods.6)Don’t forget that when using kRunCacheManager.sh, it will always flush selected caches on allnodes of your PPM cluster, but it will reset caches statistics and force garbage collection only on the node it is connected to.Flushing the PPM cache with kRunCacheManager.sh and ksc_flush_cache There are two ways to flush a PPM Cache in a manual or automated way: kRunCacheManager.sh (command line tool), or ksc_flush_cache (special command). They should be called after modifying the data directly in the database without going through one of the supported PPM interfaces (Web UI, SOAP Web Service, REST Web Service, etc.).kRunCacheManager.shkRunCacheManager.sh is a shell script that is run from the command line.Syntaxsh ./kRunCacheManager.sh [<URL>] <cache number>-“URL” parameter is optional. If omitted, it will connect to the first running RMI_URL defined in server.conf. You can pass multiple RMI urls, separated with semicolons (‘;’), and it will connect to the first running one. It is safe to omit this parameter unless you want to connect to a specific PPM node, for example to reset cache statistics or request a garbage collection.-“Cache Number” parameter is the number next to the cache that you want to flush. In order to view the list of caches with their number, run the command without any parameter to list all caches and be prompted for possible options. You can also input a letter to trigger thefollowing actions:o A: Flush All Caches. It is strongly advised not to use this option when runningkRunCacheManager in an automated way.o B: Flush Validation Caches. This will only flush the validation related caches. It can be used when validation definition or values are directly edited in PPM Database.o C: Reset Cache Statistics Counters. This only affects the node you are connected to.o D: Force Garbage Collection.Issues & Limitations-The order of the caches in the list is not consistently enforced and can vary between environments or PPM versions. As a result, if you do flush a specific cache designated by itsnumber in a script, it’s possible that the corresponding cache may change at some point in the future. You should verify that the cache numbers haven’t changed after every PPM upgrade or environment change.-It is not possible to only flush one entity in a cache; the whole cache has to be flushed. This can result in performance impact as all objects from the flushed cached will need to be reloaded.This could have performance impact under heavy load if some caches are flushed too often.-It is strongly advised NOT to use the “flush all caches” option (“kRunCacheManager.sh A”) in an automated way, as it may have performance impact under heavy system load.-If the cache is flushed using kRunCacheManager.sh while the cache maintenance thread is running (it runs every 10 seconds by default), an exception may be fired and thekRunCacheManager.sh cache flush action may be ignored.ksc_flush_cacheksc_flush_cache is a PPM Special Command that can be invoked from any command step (workflow step, PPM report command step, etc.).It only works with new caches.Syntaxksc_flush_cache <cache-name> [<id>]-“cache-name” parameter is the name of the new cache, as defined in cache.conf. For example, in the following cache.conf line:cache.datasource.title = Dashboard Datasourcesthe cache name is datasource.-“id” parameter is optional. If omitted, the cache is flushed from all its entities. If specified, only that entity will be removed from the cache.Issues & Limitations-ksc_flush_cache only works with new caches .-As of PPM 9.30, ksc_flush_cache is an undocumented (though officially supported) special command.-As of PPM 9.30, passing an entity ID to ksc_flush_cache will only work when the cache key is an Integer value. If it is a String value, it will not be flushed, and the only option to remove thedesignated entity will be to flush the whole cache.PPM Cache changes in PPM 9.31Following changes have been done to PPM Cache in 9.31 in order to correct existing issues and limitations.Conversion from legacy cache to new cacheAll the legacy caches listed in kRunCacheManager.sh but one (Scoring Criteria) have been converted to new cache.All these caches are now configured from cache.conf, and their parameters in tune.conf (orserver.conf/admin console) have been deprecated and are not used anymore.Simplification of new cache configurationSome parameters in cache.conf have been removed in an attempt to simplify cache configuration.-The only parameter that can be tuned for all caches is the cache size (parameter “maxSize”).-Parameters “maxAge”, “maxIdleTime”, “resolver” and “stalenessCheckGraceInterval” have been removed.-Parameter “distributed” is inferred automatically based on whether a staleness check in defined (distributed = false) or not (distributed = true).-Cache is automatically set to disabled if maxSize = 0.A staleness check has also been added for request types and table components; even though it’s not enabled by default, if one relies on direct DB upd ates to modify request types or table components, it’s preferable to enable the staleness check rather than disable the cache. Staleness check will only work if column LAST_UPDATE_DATE is modified during data update.One side effect of cache simplification is that the cache maintenance thread (previously used to enforce maxAge and maxIdleTime of cached objects) is now only used to reload the cache.conf configuration when modified at runtime. It doesn’t cause issues anymore when running at the same time as kRunCacheManager.sh.Changes to CacheManager Statistics report-Flush counts of types “old” and “idle” have been removed.-“Cache Flush All” count has been added. It displays the number of times the whole cache has been flushed. It helps identifying abuses of “kRunCacheManager.sh A” or of unnecessary fullcaches flushes.Running “kRunCacheManager.sh A” will increment this value by 1 for all caches.Changes to kRunCacheManager.sh-The order of listed caches has changed: it still lists legacy cache followed by new caches, but now the new caches are ordered alphabetically by cache name.-When listing all caches, the cache name of new caches is displayed in parenthesis after the cache title.-When flushing new caches, you can now use the cache name in place of the cache number. It is advised to always use the cache name, as it doesn’t rely on any ordering of caches in that list.-An extra optional parameter has been added to the command, to pass the entity ID to flush. So you can now flush one specific entity from a cache using kRunCacheManager.sh using thefollowing syntax:sh ./kRunCacheManager.sh [<URL>] <cache name (or cache number)> [<entity ID>] - A new action (E) has been added, that lists all keys in each of the new caches along with their type (String or Integer). This can help diagnose whether a specific entity is currently stored inthe cache or not. Note that in MLU environments, the same key can be displayed multiple times if it is stored in the cache using different languages.Changes to ksc_flush_cache-Passing an entity ID to ksc_flush_cache will now work regardless of the key type (String or Integer).-You can now flush the legacy caches by passing their cache number (as inkRunCacheManager.sh) instead of the cache name. Since there is only one legacy cache left in9.31, it means passing “1” as the cache name to flush the “Scoring Criteria” cache.More questions? Need help?Join the conversation and ask your questions on:- HP PPM Customer Support forum (if you are an existing HP PPM Center customer):/t5/Project-and-Portfolio-Management/bd-p/project-portfolio-mgnt-cust-forum- Public HP PPM Support and News forum:/t5/Project-and-Portfolio-Management/bd-p/itrc-935。