精华内容
下载资源
问答
  • profile:gh repo view --web
  • iOS开发Provisioning profile解析

    千次阅读 2015-10-08 19:21:57
    一般在我们代码编写中不会用到Provisioning profile这个玩意,就算是在模拟器下运行也不会碰到,但是当我们要在真机上运行时,那就必须会碰到Provisioning profile了。Provisioning profile是iOS下的配置文件。目前...

           一般在我们代码编写中不会用到Provisioning profile这个玩意,就算是在模拟器下运行也不会碰到,但是当我们要在真机上运行时,那就必须会碰到Provisioning profile了。Provisioning profile是iOS下的配置文件。目前随着Xcode7的发布,我们就可以在不购买苹果开发者账号的情况下进行真机运行,这个Provisioning profile的理解就更为简单了。

           Provisioning profile一般包括三样东西:证书、App ID、设备。当我们在真机运行或者打包一个项目的时候,证书用来证明我们程序的安全性和合法性(也类似Android中的证书keystore文件)。App ID就是你应用的ID,用来验证bundle ID是否与其一致,这个在新建项目的时候生成,当然你也可以修改;

    设备就是就是你要运行的真机,要进行授权。Provisioning profile的作用就是把这些东西打包在一起,以便在调试和发布的时候使用。

          当然Provisioning profile也分为Development和Distribution,也就是分为开发用的配置文件和发布用的配置文件。我们可以来看一下这幅图:

    其中设备ID我们可以从Xcode-->Windows-->Devices来获取:


         那我们如何来查看当前Xcode中有哪些Provisioning profile呢?通过Xcode-->Preferences-->Accounts-->View Details来进行查看。如图:

    .


          程序在真机上是怎样运行的呢?来看下图:

    .


    github主页:https://github.com/chenyufeng1991  。欢迎大家访问!


    展开全文
  • Profile使用

    千次阅读 2010-01-19 15:07:00
    Profile的组成 Profile包括3个命令行工具:PREP,PROFILE,PLIST。可以以命令行方式运行Profile,其过程是:PREP读取应用程序的可执行文件并生成一个.PBI文件和一个.PBT文件;PROFILE根据.PBI文件,实际运行并分析...

    帮助你分析并发现程序运行的瓶颈,找到耗时所在,同时也能帮助你发现不会被执行的代码。从而最终实现程序的优化。

    Profile的组成

       Profile包括3个命令行工具:PREPPROFILEPLIST。可以以命令行方式运行Profile,其过程是:PREP读取应用程序的可执行文件并生成一个.PBI文件和一个.PBT文件;PROFILE根据.PBI文件,实际运行并分析程序,生成.PBO输出文件;PREP再根据.PBO文件和.PBT文件,生成新的.PBT文件;PLIST根据.PBT文件生成可阅读的输出。

    Profile的具体功能

       Function timing:对程序花费在执行特定函数上的时间进行评估。可以通过Profile对话框激活该功能。分析结果中,Func Time一栏以秒为单位记录了函数运行所花时间,下一栏显示了该函数时间占总运行时间的百分比;Func+Child Time栏记录了函数及其所调用的子函数运行所花的总时间,下一栏显示了前述时间占总运行时间的百分比;Hit Count栏记录函数被调用的次数;Function栏显示函数的名称。

       Function coverage:记录特定函数是否被调用,可以用来确定代码中的未执行部分。可以通过Profile对话框激活该功能。分析结果列出所有被分析的函数,并使用*号标记执行过的函数。

       Function counting:记录程序调用特定函数的次数。在Profile对话框中选择Custom,并在Custome Settings中指定fcount.bat(位于VC98/bin目录下)。需要注意的是,在指定fcount.bat所在目录时,最好不要用长文件名的方式,这样有可能出错,比如要将c:/Program Files写成c:/Progra~1

       Line counting:记录程序所执行的代码中特定行的次数。在Profile对话框中选择Custom,并在Custome Settings中指定lcount.bat(位于VC98/bin目录下)。该功能使用.EXE中的调试信息启动Profile,因此不需要.MAP文件。分析结果中,Line栏标示源代码的行号,Hit Count栏记录该行执行次数,下一栏显示了该行执行次数占所有代码行执行次数的百分比,Source Line显示了对应的源代码。

       Line coverage:记录代码中的特定行是否被执行,可以用来确定代码中的未执行部分。可以通过Profile对话框激活该功能。分析结果列出所有被分析的代码行,并使用*号标记执行过的行。由于Line coverage只记录代码行是否被执行过,所以其执行开销要比Line counting小。

       此外,Profile对话框还提供了Merge功能,用以把多次运行Profile之后的统计结果组合起来。如果你正在使用Function coverage功能,则会看到是否测试了所有函数;如果你正在使用Function timing功能,则会看到以往分析与本次分析所有合并运行的累计时间。

    IDE环境下Profile的使用

       对于涉及函数分析的功能

    • 选择Project->Settings->Link,选择Enable profiling复选框
    • 重建项目
    • 选择Build->Profile,弹出Profile对话框
    • 做必要设置后,选择OK,开始运行程序

       对于涉及行分析的功能

    • 选择Project->Settings->Link,选择Enable profiling复选框和Generate debug info复选框
    • 选择Project->Settings->C/C++,选择Line Numbers Only
    • 重建项目
    • 选择Build->Profile,弹出Profile对话框
    • 做必要设置后,选择OK,开始运行程序

    配置Profile的三种方式

       修改profiler.ini文件

       profiler.ini位于VC98/bin目录下,在其[profiler]段中,你可以指定不参与分析的LIB文件或OBJ文件。比如:

    [profiler]

    exclude:user32.lib

    exclude:gdi32.lib

       Profile对话框中指定选项

       若你选择了Funciton timingFunction coverageLine coverage选项,则你可以在Advanced settings中指定进一步的范围,比如:你希望Profile只分析SampleApp.cpp文件中特定范围内的代码,可以在Advanced settings中填入, /EXCALL /INC SampleApp.cpp(30-67) 。又如:你希望file1.objfile2.obj不参与分析,则可以在Advanced settings中填入, /EXC file1.obj /EXC file2.obj 。再如:你希望只描述指定函数,则可以在Advanced settings中填入, /SF ?SampleFunc@@YAXPAH@@ ,紧跟SF参数的是特定函数的修饰符名,获取该名称的最简单的方式是在创建项目时生成的MAP文件中查找。

       SFEXCALLEXCINC都是PREP的命令行参数,有关其他参数的详细说明可以通过在命令行提示符输入PREP /H得到。

       编写批命令文件

       可以参考fcount.batfcover.batftime.batlcount.bat以及lcover.bat

    Profile中输出数据

       PLIST /T命令允许PLIST.PBT文件内容以制表格式输出到文本文件中,该格式适合输入到电子表格或数据库中。比如:PLIST /T MYPROG > MYPROG.TXT,生成的MYPROG.TXT可以利用profiler.xlm(位于VC98/bin目录下)导入到Microsoft Excel电子表格中。

    注意

       通常,分析整个程序的意义不大,因为大多数Windows应用程序,主要时间花费在消息等待上,因此精确定位要分析的代码,可以加快Profile的执行速度,提高其分析准确度。在Profile执行期间尽量关闭其他不相干的应用程序。

       若启用了远程调试,则不能够从Build菜单中调用Profile功能。

       对于inline函数,编译器以实际代码替换函数调用,因此inline函数不生成.MAP文件或CALL指令,所以当执行这样的函数时,Profile将无法得知,花费时间、运行次数等数据都归属于调用该函数的函数。Profile可以提供有关inline函数的行一级的运行次数和覆盖信息。

       对于多线程应用程序,Profile的行为取决于你所选择的分析方式,对于Line countingLine coverageProfile并未区分线程之间有何不同,它将包含当前运行的所有线程。对于Function timingFunction coverageFunction counting,分析结果取决于线程,你可以用以下方式分析一个独立线程:

    • 将线程的主函数声明为初始函数(用PREP /SF选项)
    • 包含程序中的所有函数(不要使用PREP /EXC选项)

       否则,分析结果很难解释。

    ---------------------------------------------------------------------------------------

    Profiler Errors PRF1005 through PRF4642

    The following descriptions cover Profiler Errors PRF1005 through PRF4642:

    Profiler Error PRF1005
    fatal error -- common -- operating system ran out of memory

    There is not enough memory to run this profiler module.

    Profiler Error PRF1011
    fatal error -- common -- cannot open file filename

    The profiler module could not find the specified file.

    Profiler Error PRF1012
    fatal error -- common -- cannot read expected number of bytes from file filename

    The profiler module could not read the expected number of bytes. This error is often caused by trying to profile an .EXE or .DLL file that was not linked with profiling enabled (/PROFILE linker command-line option).

    Profiler Error PRF1013
    fatal error -- common -- cannot write expected number of bytes to file filename

    The profiler module could not write the expected number of bytes. Perhaps the disk is full or the file is read-only.

    Profiler Error PRF1101
    fatal error -- common -- missing option specifier

    A / or - character was not followed by a command-line option specifier sequence. Check the command line.

    Profiler Error PRF1102
    fatal error -- common -- option: invalid option

    An invalid option was found on the command line. Check the command line.

    Profiler Error PRF1103
    fatal error -- common -- option option requires an additional parameter.

    This option was not followed by the correct number of parameters. Check the command line.

    Profiler Error PRF1104
    fatal error -- common -- option option requires a numeric parameter

    A numeric parameter was expected for this option but was not found. Check the command line.

    Profiler Error PRF1105
    fatal error -- common -- option option specified more than number times

    An option was specified too many times. Check the command line.

    Profiler Error PRF1201
    fatal error -- common -- missing filename after @

    The @ character is supposed to be followed by a response filename. Check the command line.

    Profiler Error PRF1202
    fatal error -- common -- response files nested too deeply
    Response files can be nested eight deep. Perhaps a response file calls itself recursively.

    Profiler Error PRF1301
    fatal error -- common -- file filename has an incorrect (old) signature

    A PBI, PBO, PBT, _XE, or _LL file does not contain the correct header bytes. Perhaps the file is corrupted or was created by an old version of the profiler.

    Profiler Error PRF1302
    fatal error -- common -- PBI file filename has an incorrect (old) version number

    A PBI file does not contain the correct version number. Perhaps the file is corrupted or was created by an old version of the profiler.

    Profiler Error PRF1303
    fatal error -- common -- PBT file filename has an incorrect (old) version number

    A PBT file does not contain the correct version number. Perhaps the file is corrupted or was created by an old version of the profiler.

    Profiler Error PRF1304
    fatal error -- common -- PBT or PBO file filename conflicts with current profiling state

    There was an attempt to merge a PBT or a PBO file into another PBT file with a different profiling mode selected.

    Profiler Error PRF1306
    fatal error -- common -- PBT or PBO file filename is not derived from same PBI file

    The PBT, PBO, and PBI files are not properly synchronized. Run PREP Phase I again.

    Profiler Error PRF1307
    fatal error -- common -- CPU type of module module is different from initial one

    CPU types for different modules don't match. All modules must be compiled for the same CPU type.

    Profiler Error PRF1401
    fatal error -- common -- filename: not a portable executable file

    Function profiling only: The specified executable file is not a standard executable file for Windows NT 4.0 or Windows 2000. Perhaps it is a 16-bit executable for Windows 3.x.

    Profiler Error PRF1421
    fatal error -- PREP I -- no input specified

    There were no input modules specified for PREP Phase I. Check the command line.

    Profiler Error PRF1422
    fatal error -- PREP I -- syntax error in /EXC or /INC specification: specification

    The /EXC and /INC options require function names or filenames. This specification could not be decoded. Check the command line.

    Profiler Error PRF1423
    fatal error -- PREP I -- number of modules exceeds number

    The maximum number of modules has been exceeded. Restructure the merge procedure to include more stages.

    Profiler Error PRF1424
    fatal error -- PREP I -- Debugging information in filename is not the right format for profiling, relink with /PROFILE

    Could not use debuggine information stored in the Program Database. Debug information, to be used, must be stored in the executable in old-style format. Relink with the /PROFILE option to do this.

    Profiler Error PRF1425
    fatal error -- PREP I -- filename: invalid runtime relocation, try relink

    The profiler found bad relocation information in the program to be profiled. This is usually caused by using an obsolete version of the linker. Relink your code with the new profiler and run PREP again.

    Profiler Error PRF1426
    A fixed image executable cannot be profiled, relink file without the /fixed switch.

    This error can also be caused by omitting the /PROFILE option on the LINK command line.

    Profiler Error PRF1427
    Executable image too large to profile - try breaking it down into smaller DLLs.

    The executable cannot be profile at its present size.

    Profiler Error PRF1441
    fatal error -- PROFILE -- filename: not a valid Win32s executable file

    Win32s only. The Win32s extension could not load this file. Perhaps the file is corrupted, has not been prepared for profiling, or is not a graphical user interface application. If the file were a 16-bit executable, error message 1401 would be issued.

    Profiler Error PRF1442
    fatal error -- PROFILE -- timestamp of executable has changed since PREP was run

    The PBI file was created from an older EXE file. This means that the processed executable file has changed since it was originally created by PREP Phase I. Run PREP Phase I again.

    Profiler Error PRF1443
    fatal error -- PROFILE -- cannot run program filename

    The profiler could not load the EXE file. Check that the original EXE file does run under Windows NT 4.0 or Windows 2000.

    Profiler Error PRF1444
    this version of Windows does not support this manner of profiling

    The function timing (/ft) option is not supported for this version of the Windows system.

    Profiler Error PRF1445
    Line count and line coverage are not supported on Win32S.

    The Win32S version of the profiler does not support line count or line coverage profiling.

    Profiler Error PRF1461
    fatal error -- PREP II -- no PBT output file specified

    Neither the /OT nor /M option was specified. Check the command line.

    Profiler Error PRF1462
    fatal error -- PREP II -- no PBT input file specified

    Neither the /IT nor /M option was specified. Check the command line.

    Profiler Error PRF1463
    fatal error -- PREP II -- module: different clock/sampling frequency

    The sampling frequency for this module is different from that of other modules that were profiled. Rerun PROFILE again for all modules, using the same sampling frequency.

    Profiler Error PRF1465
    fatal error -- PREP II -- CPU type in PBT or PBO file filename conflicts with current one
    Occurs only during PREP merging. The CPU type does not match the CPU type used to generate the incoming PBT or PBO files. All profiler steps must be run on the same type of computer.

    Profiler Error PRF1481
    fatal error -- PLIST -- option inconsistent with sorting type

    The options for PLIST depend on the kind of profiling being done. This error occurs, for example, when the Sort By Name option is specified for a line profiling run.

    Profiler Error PRF1482
    fatal error -- PREP or PROFILE -- abnormal termination in PREP or PROFILE detected, PLIST cannot continue

    The files output by PREP or PROFILE were not valid because one of these utilities did not complete its task. This error is usually caused by an error during the execution of PREP or PROFILE, such as a missing .MAP file.

    Profiler Error PRF1504
    fatal error -- common -- illegal fixup address in mapfile filename

    The mapfile lists all link-time fixups (including all the function call sites). This error indicates that one of the fixups was illegal, perhaps because the mapfile was not generated by the same link as the corresponding EXE (or DLL). This error is often preceded by the warning (PRF4528) about the EXE and mapfile timestamps being out of sync.

    Profiler Error PRF1521
    fatal error -- PREP I -- no functions were marked for profiling in module module

    Function profiling only: at least one function must be included for profiling in each module. Check the /INC, /EXC, and /EXCALL options on the command line.

    Profiler Error PRF1522
    fatal error -- PREP I -- more than one function matched entry specification: funcname1 and funcname2
    Function profiling only: there were two or more functions with matching names. Perhaps these are C++ overloaded functions. Use decorated names to specify the functions.

    Profiler Error PRF1523
    fatal error -- PREP I -- filename is not profiled, and can not import modified version version
    For function-level profiles, PREP uses modified EXEs and DLLs, with modified names with extensions _XE and _LL. If any modules listed in the import table of a profiled module refer to another profiled module, but the imported module is itself not being profiled, then the import table of that imported module cannot be changed, and this error occurs. The solution is to include the offending module in the profile.

    Profiler Error PRF1524
    fatal error -- PREP I -- Debugging info in filename is not the right format for profiling, relink with /PROFILE

    You must link executable files with profiling enabled (the /PROFILE linker option) to profile them. Change your linker options, rebuild, and re-run PREP.

    Profiler Error PRF1542
    fatal error -- PROFILE -- cannot set or delete environment variable var

    Function profiling only: The specified environment variable was unavailable.

    Profiler Error PRF1543
    fatal error -- PROFILE -- NtQueryIntervalProfile: NT internal error number occurred

    A Windows NT 4.0 or Windows 2000 error was detected.

    Profiler Error PRF1544
    fatal error -- PROFILE -- NtSetIntervalProfile: NT internal error number occurred

    A Windows NT 4.0 or Windows 2000 error was detected.

    Profiler Error PRF1545
    fatal error -- PROFILE -- function sampling is no longer supported

    Function sampling is not supported in this version. Use function timing to get more accurate results.

    Profiler Error PRF1621
    fatal error -- PREP I -- no debugging information in file filename

    Line profiling only: debugging information must be included in the executable file. Run the compiler and linker again with the debugging options set.

    Profiler Error PRF1622
    fatal error -- PREP I -- no source lines marked for profiling in module module

    Line profiling only: at least one line must be included for profiling in each module. Check the /INC, /EXC, and /EXCALL options on the command line.

    Profiler Error PRF1641
    fatal error -- PROFILE -- user-defined breakpoint found at address

    Line profiling only: No breakpoints may be set in the executable modules being profiled. These are not breakpoints set by the debugger but rather embedded INT 3 instructions. This error is only fatal if the INT 3 instruction is encountered during the execution of your program.

    Profiler Error PRF1642
    fatal error -- PROFILE -- unexpected single-step exception occurred at address

    Line profiling only: There was a problem with the executable file. Try relinking and rerunning PREP Phase I.

    Profiler Error PRF1643
    fatal error -- PROFILE -- an access violation occurred at address

    Line profiling only: There was a problem with the executable file. Try relinking and rerunning PREP Phase I. Check the EXE file with the debugger.

    Profiler Error PRF2541
    error -- PROFILE -- cannot start sampler

    Perhaps the executable program is too large.

    Profiler Error PRF2542
    error -- PROFILE -- cannot stop sampler

    Perhaps the executable program is too large.

    Profiler Error PRF4101
    warning -- common -- option option overrides an earlier option

    Two or more mutually exclusive switches were specified, or the same switch was specified more than once. The last switch takes precedence.

    Profiler Error PRF4106
    warning -- common -- function/source/object/lib name was never matched

    The program element was not found. Make sure the name was spelled or decorated correctly.

    Profiler Error PRF4107
    warning -- common -- /SF option not valid for line-level or sample profiles

    The start function option should be used only with function timing, function counting, or function coverage profiling.

    Profiler Error PRF4111
    warning -- common -- no error file (/E) specified for /A option

    The /A option cannot be used without the /E option. The /A option is ignored and the error output sent to stdout.

    Profiler Error PRF4421
    warning -- PREP I -- an offset duplication was detected

    There appears to be a problem with the (codeview) line number debug information. Perhaps there is an aliasing problem.

    Profiler Error PRF4422
    warning -- PREP I -- filename imports unknown module module

    PREP searches for imported modules (mostly DLLs) in the following sequence:

    • Directory PREP itself lives in
    • Current directory
    • Windows directories
    • Directories on the path

    Because the current directory depends on the profiler rather than on the profiled program, all modules might not be found. In most cases, this warning is not serious. However, if profiling leads to a GP fault (or to incorrect behavior), it might be necessary to include the "unknown module" in the profile.

    Profiler Error PRF4423
    warning -- PREP I -- filename: ignoring unknown runtime relocation type, verify linker version

    (MIPS Specific) The profiler found bad relocation information in the program to be profiled. This is usually caused by using an obsolete version of the linker. Relink your code with the new profiler, and run PREP again.

    Profiler Error PRF4481
    warning -- PLIST -- clock frequency is zero

    The clock frequency field in the PBT file has not been filled in yet, perhaps because the user has not done a profile yet, or has not merged his PBO file into his PBT file. Running PREP /M should fix the problem.

    Profiler Error PRF4521
    warning -- PREP I -- INIT environment variable not defined

    The INIT environment variable should point to the directory that contains TOOLS.INI. Set the INIT environment variable to the directory containing your TOOLS.INI and rerun PREP.

    Profiler Error PRF4522
    warning -- PREP I -- 'publics' section not found in mapfile filename

    The mapfile is corrupt.

    Profiler Error PRF4523
    warning -- PREP I -- 'static symbols' section not found in mapfile filename

    The mapfile is corrupt.

    Profiler Error PRF4524
    warning -- PREP I -- entry function function not found

    PREP could not find the specified start function (entry function) in the mapfile (see /SF switch). Perhaps the function name is misspelled.

    Profiler Error PRF4525
    warning -- PREP I -- cannot profile function function in file filename

    A special function such as setjmp was specified.

    Profiler Error PRF4526
    warning -- PREP I -- module module already includes profiler DLL filename

    The specified EXE or DLL already imports from PROFILER.DLL. The EXE (or DLL) may have been modified by PREP using the /OM switch and then renamed (from app._XE to app.EXE) before PREP was run again. Make sure that the module (EXE or DLL) specified is the original module and a module modified by PREP.

    Profiler Error PRF4527
    warning -- PREP I -- preferred load address not found in mapfile filename; assumed address

    Current versions of the linker list the preferred load address (that is, when the EXE gets loaded at this address none of the run-time relocation addresses need to be fixed up). PREP needs this information. Somehow this information was missing from the mapfile. If the latest linker was used, the mapfile was probably edited. Regenerate the mapfile, retaining the line that states the preferred load address.

    Profiler Error PRF4528
    warning -- PREP I -- timestamps of mapfile filename and executable file do not match

    The mapfile is not properly synchronized with the executable file. Relink and run PREP again.

    Profiler Error PRF4541
    warning -- PROFILE -- module not found in PBI file filename

    An attempt was made to profile a program, but the EXE was not modified by PREP. This warning occurs while selectively profiling a DLL that is called by the EXE.

    Profiler Error PRF4621
    warning -- PREP I -- line number duplicated in file filename

    There is a problem with the line number debug information. The same line number was identified with two different addresses. This is generally not serious.

    Profiler Error PRF4641
    warning -- PROFILE -- ReadProcessMemory: internal NT error number occurred

    An internal error occurred. The profiler results may be meaningless.

    Profiler Error PRF4642
    warning -- PROFILE -- WriteProcessMemory: internal NT error number occurred

    An internal error occurred. The profiler results may be meaningless.

    展开全文
  • Matlab的Profile功能

    万次阅读 2015-06-13 10:48:45
    Matlab的Profile功能编程过程中,经常需要评估哪一部分代码比较耗费时间,这对于优化代码非常重要。Visual Studio中的profile功能可以评测,Matlab同样也有这个功能,而且使用起来也比较简单。-基本命令 profile on...

    编程过程中,经常需要评估哪一部分代码比较耗费时间,这对于优化代码非常重要。Visual Studio中的profile功能可以评测,Matlab同样也有这个功能,而且使用起来也比较简单。

    -基本命令
    profile on : 开启profile
    profile off: 关闭profile
    profile clear: 清空历史数据
    profile viewer: 查看profile 结果

    -示例1
    引自Matlab 中帮助文档:

    profile on  % 开启 profile
    plot(magic(35)) % 绘制magic矩阵
    profile viewer  % 查看profile结果
    p = profile('info');
    profsave(p,'profile_results') % 保存profile 结果

    profile结果为:
    这里写图片描述

    这个结果一目了然,各函数所占用时间、调用次数、整体分布情况一目了然,这里不再多做解释。

    -示例2
    在使用过程中,我更喜欢在workspace中输入profile view命令,调出profile查看窗口,然后直接运行要测试的程序:
    这里写图片描述
    在“运行此代码”的文本框中输入要运行的程序名字,即可得到结果。
    我要运行的代码名称为:TestAviReader.m,是一段读取和显示数据视频的简单文件。

    xyloObj = VideoReader('test.avi');
    
    nFrames = xyloObj.NumberOfFrames;
    vidHeight = xyloObj.Height;
    vidWidth = xyloObj.Width;
    
    fh = figure('Name', 'Dataset Checking');
    ah = axes('parent', fh);      
    for k = 1 : nFrames
        img = read(xyloObj,k);
        disp('当前播帧数:'),disp(k);
        imshow(img, 'Parent', ah);
        pause(0.001)
    end

    最终的profile结果为:
    这里写图片描述

    从结果来看,运行基本时间主要在imshow上。

    -参考-
    http://developer.51cto.com/art/201104/255128_all.htm


    题外话
    这次写博客也顺便体验csdn博客新编辑器,确实方便又好用。以后还是要多写,多练,以理论和思考为主,减少工程类的(比如这篇)。


    展开全文
  • memory profile there are two modes u can use in the memory profiler to inspect memory usage of your application. this is selected in the dropdown in the t...

    https://docs.unity3d.com/Manual/Profiler.html

    memory profile
    there are two modes u can use in the memory profiler to inspect memory usage of your application. this is selected in the dropdown in the top-left of the lower panel.

    detailed
    the detailed view allows u take a snapshot of the current state. use the take sample button to capture detailed memory usage. obtaining this data take some time, so the detailed view should not be expected to give u real-time details. after taking a sample, the profile window is updated with a tree view where u can explore memory usage.

    在这里插入图片描述

    this displays individual assets and game object memory usage. it also displays a reason for a game object to be in memory. common reason include:
    1/ assets: asset referenced from user or native code
    在这里插入图片描述

    2/ built-in resources: unity editor resources or unity default resources
    3/ not saved: game objects marked as don save
    4/ scene memory: game object and attached components
    5/ other: game objects not marked in the above categories

    click on a GameObject in the list to view it in either the project or the scene view.

    when profiling in the editor, all numbers displayed by the memory profile indicate the memory usage in the editor. there are generally larger than when running in a player, because running the editor adds extra memory. for more precise numbers and memory usage for your app, use the profiler connection to connect the running player. this will give the actual usage on the target device.

    展开全文
  • 1. 修改/etc/profile文件 特点:所有用户的shell都有权使用你配置好的环境变量 说明:如果你的电脑仅用作开发,建议使用此配置,...[plain] view plain copy #1:编辑/etc/profile  bixiaopen
  • Android 工具:Profile GPU Rendering

    千次阅读 2017-06-21 23:10:34
    一、Profile GPU Rendering工具Profile GPU Rendering工具对于相对于16毫秒每帧的基准花了多少时间来渲染UI,给了一个快速可视化的展示: 1. 它帮你快速查看一个UI窗口有多少超过了16毫秒每帧的目标; 2. 确定是否...
  • Almost all the implementation I see today are based on OAuth 2.0 Bearer Token Profile. Of course its an RFC proposed standard today. OAuth 2.0 Bearer Token profile brings a simplified scheme ...
  • Android 性能监测profile

    2019-01-02 15:47:45
    Android Studio自带的profile功能可以监测CPU占用,内存占用,网络使用,电量四个性能   可以看到上面四个性能的实时监测   CPU   当前APP占用cup 其他软件占用cup 当前的线程数量 我这里APP只有一个...
  • @JsonView注解

    2018-05-25 16:35:07
    使用接口来声明多个视图package org.byron4j.springMVC4_rest_jackson_jsonview_...public class Profile { public interface PublicView {} public interface FriendsView extends PublicView{} public...
  • DNN之user profile问题

    千次阅读 2008-06-27 13:10:00
    参考资料http://www.ventrian.com/Support/ProductForums/tabid/118/view/topic/postid/27303/forumid/12/tpage/1/Default.aspx看似简单的user profile添加照片,实际涉及到的DNN内部的一些实现。如参考资料上所述,...
  • Spring @Profile标签使用:

    千次阅读 2017-08-29 07:18:06
    spring中@profile与maven中的profile很相似,通过配置来改变参数。 例如在开发环境与生产环境使用不同的参数,可以配置两套配置文件,通过@profile来激活需要的环境,但维护两套配置文件不如maven中维护一套配置...
  • CCS中如何使用profile

    千次阅读 2014-10-27 17:33:20
    简单方法:profile-->clock-->enable和view,然后在想统计的区域设两个端点,将程序运行到第一个断点处(有人说用:运行到光标处的办法,有人说正常运行run到断点处,这两种方法不大一样,因为我的程序中有函数printf,...
  • 名称 Mojolicious::Plugin::ViewBuilder - 一个 Mojolicious ...= pluggable_view 'profile' %> # now, in the plugin, that will attach the new helper to the view sub register { my ( $self, $app, $conf ) = @_;
  • Freeswitch profile 配置

    千次阅读 2019-08-26 10:40:01
    freeswitch> sofia profile <profile_name> flush_inbound_reg [|] [reboot] If you leave out <call_id> and/or , you will flush/reboot every registered endpoint on a profile. Reloading profiles ...
  • 多个router-view视图嵌套: 1,除了app.vue中的router-view之外,还有其他的嵌套在router-view中的router-view视图,子路由写在router.js children中 app.vue &lt;template&gt; &lt;div id="...
  • 最近在翻Oracle SQLPLUS官方文档...PUP(PRODUCT_USER_PROFILE)介绍  PRODUCT_USER_PROFILE是SYSTEM账户下一个表,可提供用户级别的安全限制。  PUP设置对DBA权限用户无效。  PUP只针对本地数据库生效(Local Database
  • fnd_profile.value的用法

    千次阅读 2016-03-21 15:17:40
    fnd_profile.value的用法: select fnd_profile.value('gl_set_of_books_id')  from dual select fnd_profile.value('mfg_organization_id')  from dual --取子库 select fnd_profile.value('GL_SET_OF_BKS_...
  • Profile文件  配置文件编写的时,可以是application-{profile}.properties/yml,默认使用application.properties的配置; 激活指定profile(三种方式)   1、在配置文件中指定 (xxx.properties/xxx.yml)  1 ...
  • Profile-Guided Optimizations 按配置优化

    千次阅读 2018-03-19 15:10:01
    Profile-Guided OptimizationsSend Feedback on this topic to Microsoft.View this topic online in your default browser.Profile-guided optimization lets you optimize an output file, where the optimizer us...
  • 什么是View视图? Django的View是如何工作的Django的Web开发也遵循经典软件设计开发的MVC模式。View (视图) 主要根据用户的请求返回数据,用来展示用户可以看到的内容(比如网页,图片),也可以用来处理用户提交的数据...
  • spring 通过maven profile配置不同的环境多环境的配置,网上看到的都太繁琐,后来自己配置了一个简单的,供大家参考 首先配置profile环境 profiles> profile> id>localid> properties> dev.environment>...
  • 设置用户环境变量 输入命令:vim ~/.bash_profile,打开文件,输入如下内容: 范例(设置maven环境变量): export M2_HOME=~/apache-maven-3.5.2 export PATH=$PATH:$M2_HOME/bin 退出并保存:esc =&...
  • traceview使用总结

    千次阅读 2019-08-17 17:16:04
    文章目录1.traceview的用途2.生成trace文件的三种方式(1)代码生成(2)使用android studio生成(3)DDMS生成3.使用traceview打开trace文件4.分析trace文件 1.traceview的用途 traceview是Android sdk中的一个...
  • view简写 TemplateView.as_view()

    千次阅读 2019-10-17 16:06:42
    view简写 TemplateView.as_view() https://code.ziqiangxuetang.com/django/django-generic-views.html (1)如果想省略view层,直接在url层返回页面,则在本来要写view函数位置的地方写:TemplateView.as_view...
  • Camera support cross profile image capture测试失败在android 5.1系统中的verifier测试中,有一个测试项: BYOD Managed Provisioning—Camera support cross profile image capture拍完照后,去查看照片(Verify ...
  • Android 中蓝牙Profile与UUID

    千次阅读 2015-04-09 09:45:37
    在Android中,常用的几种Bluetooth Profile分别为:SPP (Serial Port Profile)、A2DP (Advanced Audio Distribution Profile)、AVRCP (Audio/Video Remote Control Profile)、HID (Human Interface Device Profile)...
  • spring @profile注解的使用

    万次阅读 2017-10-17 12:01:02
    spring @profile注解的使用 本文主要介绍spring中@profile的使用方法以及在什么情况下使用。 本文主要参考: http://www.cnblogs.com/davidwang456/p/4429058.html 好,下面上货。 首先说一下为什么要使用这...
  • Android Studio 无法使用 Profile

    千次阅读 2020-01-02 11:00:36
    目录 1、问题描述 ...Android Studio的所有项目在使用ProfileAPP功能的时候,会出现闪退问题。logcat也没报错,在Run那儿出现了如下信息 I/tpc.imon.rddan: Rejecting re-init on previously-fa...

空空如也

空空如也

1 2 3 4 5 ... 20
收藏数 80,373
精华内容 32,149
关键字:

profileview